When we enable the GPU process we try to disable all GPU content in the UI process so that we can't have GPU related crashes there. D3D9DXVAManager creates its own IDirect3DDevice9 without checking the GPU process status, so we could still end up accessing the GPU this way. It's probably very unlikely to actually have videos playing in the UI process, but this would still be good to fix.
I understand that "video decoding in GPU process" is behind a separate preference, right? So, this is just for the part that is compositor specific, and should thus move to whatever process owns the compositor?
(In reply to Milan Sreckovic [:milan] from comment #1) > I understand that "video decoding in GPU process" is behind a separate > preference, right? It is, yes. > So, this is just for the part that is compositor > specific, and should thus move to whatever process owns the compositor? It's more that we want the UI process to be blocked from using the GPU in any way when we have the GPU process, and the d3d9 decoder paths subverts our attempts to do this.
When we deal with this, we should make sure cover the scenarios where we restart the GPU process, as well as when we decide not to, and drop to software.
Mass wontfix for bugs affecting firefox 52.
status-firefox52: affected → wontfix
You need to log in before you can comment on or make changes to this bug.