Bug 1129492 will need some way for WebGL to work without the content process being an X11 client, which probably means out-of-process WebGL (unless there's some way to use EGL (bug 788319) to have content processes talk directly to the GPU for offscreen rendering and only the compositor talk to the X server, but I don't know enough about how that all works to know if that's even possible).

This bug is to track everything that needs to happen for that to be usable on Linux.

Tracking for Fission Nightly M6c.

Tracking for Fission M7 Beta milestone. This bug doesn't need to block our Fission Nightly experiment (milestone M6b) because we will exclude Linux users.

Nika doesn't think WebGL Remoting needs to block Fission MVP. Non-native theming will remove the biggest use of X11 in content processes and that's probably good enough for Fission MVP.

Early WIP, very basic skeleton status, able to run code from within
SandboxTest inside the new WebGL process.

Depends on D120241

Depends on D119533

Comment on attachment 9231935 [details]
WIP: Bug 1638466 - Move arguments parsing to ProcessChild

Revision D120241 was moved to bug 1723505. Setting attachment 9231935 [details] to obsolete.

Comment on attachment 9234015 [details]
WIP: Bug 1638466 - Refactor definition and usage of GECKO_PROCESS_TYPE()

Revision D121388 was moved to bug 1726804. Setting attachment 9234015 [details] to obsolete.

Comment on attachment 9234016 [details]
WIP: Bug 1638466 - Refactor PROCESS_TYPE_* from nsICrashService

Revision D121389 was moved to bug 1726804. Setting attachment 9234016 [details] to obsolete.

Depends on D119533

The current patch stack depends on bug 1723505 and bug 1726804 in an effort to reduce the amount of scaffolding-only required to bring up a new process. I would still like to improve especially around how the process is being launched: the current code was inspired from RDD, and while I like we expose a Promise, I'm wondering if we could make it simpler to handle and track the launch (i.e., get rid of the token thing) and/or maybe expose this promise interface directly within GeckoChildProcessHost.

Taking this bug; at this point we shouldn't need a dedicated process or anything, just flipping the pref.

https://hg.mozilla.org/mozilla-central/rev/1c322856010d

== Change summary for alert #33487 (as of Mon, 07 Mar 2022 11:27:48 GMT) ==

Improvements:

For up to date results, see: https://treeherder.mozilla.org/perfherder/alerts?id=33487

More than 100% improvement seems unlikely, but sure, theoretically possible since it was bogged down to 4fps before!