Well that was short lived ... although not totally unexpectedly. This has been disabled again for the moment, while I investigate regressions. Two of these I think are too frequent for us to carry in Nightly.
Both of these frequent ones look like they are things that are normally non-fatal issues when they happen in the content process, but I need to find the scenarios and catch them in the recording code and not when they are played back in the GPU process. Apologies for any issues this may have caused you, but if you have good steps to reproduce for any of these GPU crashes, please file them to block: https://bugzilla.mozilla.org/show_bug.cgi?id=1547286 You can still set gfx.canvas.remote to true to test this. Thanks, Bob On Wednesday, 20 November 2019 16:36:49 UTC, bo...@mozilla.com wrote: > Hi all, > > I have just landed the patch to enable moving accelerated Canvas 2D to the > GPU process on Windows. > > This is only enabled on Nightly at the moment and is part of our work to move > GPU access and win32k system calls out of the content process. > > Please file any problems you find as bugs blocking: > https://bugzilla.mozilla.org/show_bug.cgi?id=1548487 > > Thanks, > Bob _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
