Bug 1680946 Comment 2 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
(In reply to Kelsey Gilbert [:jgilbert] (previously Jeff) from comment #1)
> Parent should not have gpu access sandboxed away. I would not have expected bsd to use a gpu process? Are you sure that content tabs are using out-of-process webgl instead of in-process?

right, in about:support we have `IsWebglOutOfProcessEnabled: 0` so i guess  that means 'no' right now, but i was pretty sure that at some point there was a dedicated gpu process (since it was sandboxed/pledged in bug #1580268), but maybe with fission/webrender that changed ?
Revision 1 by
on 
(In reply to Kelsey Gilbert [:jgilbert] (previously Jeff) from comment #1)
> Parent should not have gpu access sandboxed away. I would not have expected bsd to use a gpu process? Are you sure that content tabs are using out-of-process webgl instead of in-process?

right, in about:support we have `IsWebglOutOfProcessEnabled: 0` so i guess  that means 'no' right now, but i was pretty sure that at some point there was a dedicated gpu process (since it was sandboxed/pledged in bug #1580268), but maybe with fission/webrender that changed ?

or that dedicated process is only spawned at startup to gather glx info/environment, and not used anymore for rendering at runtime ? Or some about:config knob needs to be forced on for the process to be used ?
Revision 2 by
on 
(In reply to Kelsey Gilbert [:jgilbert] (previously Jeff) from comment #1)
> Parent should not have gpu access sandboxed away. I would not have expected bsd to use a gpu process? Are you sure that content tabs are using out-of-process webgl instead of in-process?

right, in about:support we have `IsWebglOutOfProcessEnabled: 0` so i guess  that means 'no' right now, but i was pretty sure that at some point there was a dedicated gpu process (since it was sandboxed/pledged in bug #1580268), but maybe with fission/webrender that changed ?

or that dedicated process is only spawned at startup to gather glx info/environment, and not used anymore for rendering at runtime ? Or some about:config knob (`layers.gpu-process.force-enabled` or MOZ_ACCELERATED=1 ?) needs to be forced on for the process to be used ?

Back to Bug 1680946 Comment 2