[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:
Component:  Editor                               |     Version:  5.0
 Severity:  critical                             |  Resolution:
 Keywords:  needs-patch reporter-feedback close  |     Focuses:
-------------------------------------------------+---------------------

Comment (by timhibberd):

 @pento thanks for the suggestion. I agree it is a possibility. At the
 moment there are a lot of possible culprits.

 What is throwing me off is that I have been using this Docker-for-Windows
 setup with WordPress 4.x for over a year with most containers running
 WordPress mounted on the local disk AND the V5Beta WordPress container
 instance presently giving me grief worked fine for all V5 releases up to
 and including v5Beta3. The trouble only started in v5Beta4.

 So I am focusing on the deltas...what has changed and what is different.

 The container-based V5 WordPress causing trouble is different from all the
 others that work fine in the following ways:

 1) I upgraded PHP on the server in the container from PHP7.0 to PHP7.2.
 All my other containers that work fine are running PHP7.0

 2) XDEBUG was installed and enabled on this container only. XDebug is not
 installed / enabled on the other containers that work fine

 3) This is the only container with a WordPress that has been updated daily
 with nightly V5Beta releases since early V5Beta releases were made
 available...is this just a corrupted upgrade sequence! Maybe!

 So with all the possibilities including a build corrupted somehow through
 the nightly Beta build upgrades I think my prudent next step is to try to
 recreate an environment with the same problems.

 I will poke at this container instance a bit but I am reluctant to invest
 too much of my time and valuable time of contributors such as yourself on
 what is quite possibly a red herring.

 I just don't want to give up too quickly and find out later through
 failures in the field that there is a REACT / Webpack race-condition. Race
 conditions are hard to reproduce so if this is one, this container is a
 debug goldmine. I am targeting to diagnose this issue or close it as a red
 herring by mid next week.

 Thanks for your help. Much appreciated :-)

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