(In reply to voracity from comment #66) > This just affected me after upgrading to 1903. Disabling gfx.webrender.dcomp-win.enabled fixed it. Are there any negative consequences to that flag? Only known problem was performance decrease. > Given that the Windows fix is in the 20H1 preview release, does this mean the fix won't be available for at least another 8 months? Installing KB4512941 seemed to address the problem for me. :voracity, can you check if the problem is addressed with it? https://support.microsoft.com/en-us/help/4512941/windows-10-update-kb4512941
Bug 1556634 Comment 67 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to voracity from comment #66) > This just affected me after upgrading to 1903. Disabling gfx.webrender.dcomp-win.enabled fixed it. Are there any negative consequences to that flag? Only known problem was performance decrease. > Given that the Windows fix is in the 20H1 preview release, does this mean the fix won't be available for at least another 8 months? Installing KB4512941 seemed to address the problem for me. It was released on August 30. :voracity, can you check if the problem is addressed with it? https://support.microsoft.com/en-us/help/4512941/windows-10-update-kb4512941