Firefox can Crash when failing to Create a Wayland Subsurface
Categories
(Core :: Widget: Gtk, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox131 | --- | fixed |
People
(Reporter: sarah, Assigned: stransky)
Details
Attachments
(2 files)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:129.0) Gecko/20100101 Firefox/129.0
Steps to reproduce:
When testing an in-development Wayland Compositor, a Firefox process segfaulted during setup. I have attached the minidump-stackwalk output.
Actual results:
From the stack dump it appears as if while attempting moz_container_wayland_surface_create_locked, Firefox assumes wl_subcompositor_get_subsurface Firefox ends up passing a null pointer through to wl_proxy_marshal_constructor in libwayland-client
Looking at the code...I believe this is because the Compositor did not advertise support for the wl_subcompositor global interface and Firefox did not check the output of WaylandDisplayGet()->GetSubcompositor() prior to passing it into wl_subcompositor_get_subsurface
Expected results:
Firefox should fail gracefully in the presence of incomplete compositors / malformed compositor protocol setups.
Comment 1•9 months 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.
Assignee | ||
Comment 2•9 months ago
|
||
We're expected to have a subcompositor:
https://searchfox.org/mozilla-central/rev/e942f7bc56cd103bba86b396ddeba5b1ab04f1a4/widget/gtk/nsWaylandDisplay.cpp#208
Assignee | ||
Comment 3•9 months ago
|
||
Updated•9 months ago
|
Comment 5•9 months ago
|
||
bugherder |
Description
•