[wp-trac] [WordPress Trac] #45341: WSOD when editing a page (Issue introduced between v5Beta3 and v5Beta4)

[WordPress Trac]

#45341: WSOD when editing a page (Issue introduced between v5Beta3 and v5Beta4)
--------------------------------------+------------------------------
 Reporter:  timhibberd                |       Owner:  (none)
     Type:  defect (bug)              |      Status:  new
 Priority:  normal                    |   Milestone:  Awaiting Review
Component:  Editor                    |     Version:  5.0
 Severity:  critical                  |  Resolution:
 Keywords:  needs-patch dev-feedback  |     Focuses:
--------------------------------------+------------------------------

Comment (by timhibberd):

 Cheers @Ipstenu - I have been hoping some others might add further insight
 to this issue. My problems literally commenced with the upgrade from
 v5Beta3 to v5Beta4. No change on the system on my side and it went from
 working to non-working GB edits with the upgrade. So something changed
 between v5Beta3 and v5Beta4 that would be a natural suspect in the
 generation of these Javascript errors. Was there a Webpack version upgrade
 at that time?

 My installation is just WordPress with a few debugging plug-ins (disabling
 the plug-ins does not change anything).

 For those joining this thread in the middle, the WSOD is not caused by a
 PHP error. The page is being delivered in entirety and the WSOD is caused
 by Javascript errors within REACT code with a number being Webpack
 related. Displaying existing pages built with previous GB editor works
 fine but I can no longer add / edit pages.

 I will do more testing to try to identify any common patterns. At the
 moment the errors look like random concurrency issues related to dynamic
 loading of REACT / DOM elements. I'm new to REACT so it will take me time
 to be more specifically helpful.

 The only thing I am doing that may be different from others  is that I am
 running this under Docker for Windows. It is possible that this
 configuration varies the timing sufficient to show race-conditions that
 others don't see using a conventional installation. I have done some
 Google searching and it looks like REACT is not a linear renderer and uses
 a number of concurrency and asynchronous rendering tricks to make the
 render appear to be faster and more fluid. At the moment this is what this
 error looks like to me. Concurrency race-conditions.

 I'll test and research further. It would be good if there was at least
 someone else experiencing fatal JavaScript errors so we could compare set-
 ups.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/45341#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform