This is a meta/tracking bug for prototyping out-of-process compositing. We believe this has significant benefits for reliability/stability, as the more GPU work we can move out of the UI process, the less likely Firefox is to crash. D3D11 crashes and device resets will be much easier to handle as we can simply restart the GPU process if something goes wrong.
Initially we are only remoting composition - this prototype does not involve remoting rasterization, video acceleration, or GL commands. Firefox will still use the GPU in content processes, and the parent process in non-e10s mode (or in e10s mode when content is accelerated).
Release Note Request (optional, but appreciated)
[Why is this notable]:
[Affects Firefox for Android]:
[Suggested wording]: Added process separation for faster graphics performance
[Links (documentation, blog post, etc)]: https://ashughes.com/?p=374
Added to Fx53 Aurora release notes.