KDE Wayland + force enabled OS compositor: Firefox crashes when trying to render a menu
Categories
(Core :: Widget: Gtk, defect)
Tracking
()
People
(Reporter: filippo27998, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
15.11 KB,
text/plain
|
Details |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:90.0) Gecko/20100101 Firefox/90.0
Steps to reproduce:
- Start Firefox in a native Wayland session (KDE, not XWayland)
- Try to open any menu (hamburger menu, right click menu, menu bar)
Actual results:
- Firefox crashes, generating a crash report. This happens consistently.
Comment 1•4 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
After additional testing, the problem seems to be related to force-enabling the webrender compositor (gfx.webrender.compositor.force-enabled: true). Disabling this allows normal use of Firefox with webrender under Wayland, but did not cause issues on previous Firefox versions.
Can you please submit the crash report and post its ID here?
Thanks.
(In reply to Martin Stránský [:stransky] (ni? me) from comment #3)
Can you please submit the crash report and post its ID here?
Thanks.
Can this me this one?
https://searchfox.org/mozilla-central/rev/77f0b36028b2368e342c982ea47609040b399d89/gfx/layers/composite/LayerManagerComposite.cpp#172
Are you running WebRender compositor?
Robert, is that related? I see GetNativeLayerRoot() is used on the Compositor only.
Comment 6•4 years ago
|
||
(In reply to SoilpH96 from comment #4)
(In reply to Martin Stránský [:stransky] (ni? me) from comment #3)
Can you please submit the crash report and post its ID here?
Thanks.
That's bug 1718688.
Updated•4 years ago
|
Updated•4 years ago
|
Comment 8•4 years ago
|
||
Edit: wow, Darkspirit was faster than me :)
The crash report indeed says "wrCompositor":{"status":"force_enabled"}
, so looks like a dup of bug 1718688.
SoilpH96: gfx.webrender.compositor.force-enabled
should fix the issue - up until 89 it just did nothing, now there is an experimental compositor backend.
Martin, I'm sorry, I should have force disabled the setting on release :( (otoh that's the risk of enabling random settings)
In beta/91 things are already much more stable.
Description
•