webrender::render_api::Transaction::set_document_view crashes since Firefox v 101 do not happen if started with env -i
Categories
(Core :: Graphics: WebRender, defect)
Tracking
()
People
(Reporter: goran_obal, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:100.0) Gecko/20100101 Firefox/100.0
Steps to reproduce:
I'm experiencing Firefox crashes since version 101. I'm using (old) CentOS 7.3 with GNOME desktop environment. Interesting thing is that these crashes do not happen in KDE or XFCE desktop environments. Further, I have found that if I start Firefox with 'env -i' the crashes also do not happen. I am talking about this category of crashes: https://crash-stats.mozilla.org/signature/?product=Firefox&signature=webrender%3A%3Arender_api%3A%3ATransaction%3A%3Aset_document_view&date=%3E%3D2022-05-31T12%3A36%3A00.000Z&date=%3C2022-06-07T12%3A36%3A00.000Z&_columns=date&_columns=product&_columns=version&_columns=build_id&_columns=platform&_columns=reason&_columns=address&_columns=install_time&_columns=startup_crash&_sort=-date&_sort=-version&page=1
They have all in common that some nonsensical window size was trying to be allocated (for example: Attempting to create a 28117x32840 window/document).
This, however, fixes it for me (starting firefox from the terminal, shell is bash):
env -i DISPLAY=:0 ./firefox/firefox
I have tried it with Firefox 101 and with beta 102b4 - it's the same.
Also, I have found another way that v 101 and newer do not crash with the above mentioned error: Go to Customize Toolbar and enable Title Bar (bottom left - there's a checkbox). When Title Bar is activated, I can't get Firefox to crash, but when the Title Bar is deactivated, I can crash Firefox by simply un-maximizing the window, for example.
Actual results:
Firefox crashes on startup, not even safe mode works. Editing prefs.js and enabling Title Bar, fixes this:
user_pref("browser.tabs.inTitlebar", 0);
Expected results:
Firefox should work also without Title Bar.
Comment 1•2 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 correct in case you think the bot is wrong.
Updated•2 years ago
|
Comment 2•2 years ago
|
||
Thanks for filing this and for the additional details. I'm closing this as a duplicate of bug 1695591 to keep things in one place but the additional details are very useful. I'll find some time to get back this soon.
Reporter | ||
Comment 3•2 years ago
|
||
I am glad I could help at least a little bit. If you need anything else from me or for me to test something, let me know.
Description
•