content process crash with WR? WR- but webrender is definitely enabled
Categories
(Core :: Graphics, defect, P3)
Tracking
()
People
(Reporter: tnikkel, Unassigned)
Details
I got this content process crash
https://crash-stats.mozilla.org/report/index/79367032-e054-4838-98d3-c8bbb0210201
with "WR? WR-" in it. I immediately checked about:support to see if webrender got disabled somehow but it was still enabled.
|
||
Comment 1•4 years ago
|
||
The crash report telemetry says:
{"compositor":"opengl","hwCompositing":{"status":"available"},"gpuProcess":{"status":"unused"},"wrQualified":{"status":"available"},"webrender":{"status":"disabled:FEATURE_FAILURE_USER_FORCE_DISABLED"}
which very much suggests that we think OpenGL is being currently used, and WR should have been disabled from the start either gfx.webrender.force-disabled or MOZ_WEBRENDER=0.
|
|
||
Comment 2•4 years ago
|
||
Did you expect to have WR enabled in the first place? I'm guessing you saw "WebRender" in the compositor section at the top of about:support?
|
Reporter | |
Comment 3•4 years ago
|
||
Yeah, I expect wr to be enabled. I haven't touched any setting to change that in my main profile, and my main profile has been getting webrender for a while now. Yes I checked about:support immediately after the crash and I looked at the compositor section and saw webrender. I didn't save it or check anything else there.
One thing that might affect this: I had run this copy of Firefox in another profile and it updated. When the crash happened I had just started navigation to a file:// uri, which should have brought up the "Sorry. We just need to do one small thing to keep going." page, but instead I got the tab crashed page.
Description
•