1437559 - WebRender creates crash report on shutdown on Windows without ANGLE

Status: RESOLVED WONTFIX

(Core :: Graphics: WebRender, defect, P2)

Description

[Henrik Winnemöller]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Firefox/60.0
Build ID: 20180211220056

Steps to reproduce:
1. Create a fresh profile, open about:config
2. Set "gfx.webrender.all" to "true"
3. Set "gfx.webrender.force-angle" to "false"
4. Restart Firefox using Shift+F2 "restart"


Actual results:

Firefox closes, all Firefox processes stop being listed in the Task-Manager. The browser stays closed. No crash dialog is shown, also the crash reports list on about:support is empty when opening Firefox again.


Expected results:

Firefox closes and restarts.

Comment 1

[Darkspirit]

WFM. I just see bug 1432261. (Radeon RX480 @ Win10)

Would everything work if you set gfx.webrender.force-angle back to true?

Could you please open about:support (e.g. in a fresh profile), click on the "Copy text to clipboard" button, paste it into a text file and upload it here (Attach File)? Thanks!

Comment 2

[Henrik Winnemöller]

Attachment: about:support from bug reporter

about:support from bug reporter

Comment 3

[Henrik Winnemöller]

Setting "gfx.webrender.force-angle" to "false" does deactivate WebRender completely for me since my GPU is too old to be supported by ANGLE for the required OpenGL level (NVIDIA Geforce 8600M GS). My GPU does support the required OpenGl level natively, thus the setting. Besides this issue, WebRender works quite well on this machine.

I have created an attachment containing my about:support's raw content, see https://bugzilla.mozilla.org/attachment.cgi?id=8950400

@ https://bugzilla.mozilla.org/show_bug.cgi?id=1432261: Interesting, your is WFM for me. Should I add my details on your bug?

Comment 4

[Darkspirit]

(hwinnemo from attachment 8950400 [details])
> "webgl2Renderer": "WebGL creation failed: \n* Error during ANGLE OpenGL init.\n* Exhausted GL driver caps."
-----

> My GPU does support the required OpenGl level natively, thus the setting.
Did WebRender ever work with your GPU or is this a recent regression?

> Should I add my details on your bug?
I don't think so. It seems to work for other people.

Comment 5

[Darkspirit]

Correction: Did you try the steps from comment 0 in the past and did they work?

Comment 6

[Henrik Winnemöller]

(In reply to Jan Andre Ikenmeyer [:darkspirit] from comment #4)
> (hwinnemo from attachment 8950400 [details])
> > "webgl2Renderer": "WebGL creation failed: \n* Error during ANGLE OpenGL init.\n* Exhausted GL driver caps."
> -----
> 
> > My GPU does support the required OpenGl level natively, thus the setting.
> Did WebRender ever work with your GPU or is this a recent regression?

Works like a charm :)

Besides having to change the "gfx.webrender.force-angle" flag, I never had to do any additional configuration work. The ANGLE issue was confirmed by :jrmuizel: The ANGLE team stopped supporting DX10.0 for the required OpenGl levels needed for WebRender. The WebGl 2 issue is related to this, since ANGLE requires API compatibility for WebGl 2 > DX10.0. I have other machines with more recent architectures like Fermi, Maxwell or Pascal, but those exhibit a lot of visual issues using WR that are already filed in different bugs.

> I don't think so. It seems to work for other people.
I also do have an AMD Radeon RX 460, so I could at least try to reproduce your bug :) Maybe it is something common on Polaris.

(In reply to Jan Andre Ikenmeyer [:darkspirit] from comment #5)
> Correction: Did you try the steps from comment 0 in the past and did they
> work?
The restart issue is something I did not encounter all the time, but now it has become reproducable. I guess I should try to find the regression range. I started using WR exclusively only weeks ago so it should be in this range.

Comment 7

[Darkspirit]

(In reply to hwinnemo from comment #6)
> I also do have an AMD Radeon RX 460, so I could at least try to reproduce your bug :) Maybe it is something common on Polaris.
Please! ;)

> I guess I should try to find the regression range.
That would be great. Thanks :)

https://mozilla.github.io/mozregression/install.html

Before bug 1425260 comment 9 (2018-01-11 09:43 +0000), there was no gfx.webrender.all, therefore you would have to set then:
gfx.webrender.enabled;true
gfx.webrender.blob-images;true
image.mem.shared;true
(+ gfx.webrender.force-angle;false)

-----

(In reply to hwinnemo from comment #0)
> 1. Create a fresh profile, open about:config
> 4. Restart Firefox using Shift+F2 "restart"

Doing only those two steps wouldn't cause any problem, right? Then we could set "firefox60" to "unaffected".

Comment 8

[Henrik Winnemöller]

STR (Update):
1. Be on fresh profile
2. Set "gfx.webrender.all" to "true"
3. Set "gfx.webrender.force-angle" to "false"
4. Shutdown the browser

Actual results:
The browser closes, a crash report is generated and visible in the event log (see comment https://bugzilla.mozilla.org/show_bug.cgi?id=1437442#c9).

Expected results:
The browser closes.

I can only reproduce this behaviour on this machine.

Comment 9

[Glenn Watson [:gw]]

I think we only plan to support running with ANGLE, for the foreseeable future (until there is a native D3D12 / Vulkan backend for WR).