Using the GPU process has many advantages. If there are crashes in WebRender, GPU drivers, or other instability, we can avoid a crash to the user. While this seems to work well with basic compositing, there are appear to be races when we use OpenGL or WebRender compositing. This bug tracks bugs blocking turning on the GPU process on Linux. It will be disabled in bug 1653443.

What we need for bug 1129492 is out-of-process WebGL, which means either this (and bug 1654957) or bug 1654945.

(In reply to Jed Davis [:jld] ⟨⏰|UTC-6⟩ ⟦he/him⟧ from comment #1)

What we need for bug 1129492 is out-of-process WebGL, which means either this (and bug 1654957) or bug 1654945.

Bug 1654957 has been fixed in Fx81.

Bug 1654945 was closed a dupe of bug 1669381, which was fixed last week in Fx83.

This bug's title says X11. Does it actually cover doing the same on Wayland too?

I see there's https://bugzilla.mozilla.org/show_bug.cgi?id=1481405#c15 (https://phabricator.services.mozilla.com/D32640) which seems to suggest that's not possible?

We'll see how much code can be shared:
(Martin Stránský [:stransky] (ni? me) from bug 1610199 comment 75)

This bug a blocked by Bug 1683808 (and similar). The correct way forward here is to implement GPU process on Wayland (by dmabuf EGL framebuffer) and then implement VAAPI in GPU process as we actually can't use VAAPI in RDD process.

There's also https://bugzilla.mozilla.org/show_bug.cgi?id=1653443#c7

Note that we also don't have the GPU process on Wayland and AFAIK there's no concept for how we could ever have.

Has the situation changed on Wayland since then?

(In reply to Teoh Han Hui from comment #5)

There's also https://bugzilla.mozilla.org/show_bug.cgi?id=1653443#c7

Note that we also don't have the GPU process on Wayland and AFAIK there's no concept for how we could ever have.

Has the situation changed on Wayland since then?

Yes, we need to implement it, it's Bug 1732951.