Closed Bug 1913988 Opened 9 months ago Closed 9 months ago

Firefox can Crash when failing to Create a Wayland Subsurface

Categories

(Core :: Widget: Gtk, defect)

Firefox 129
defect

Tracking

()

RESOLVED FIXED
131 Branch
Tracking Status
firefox131 --- fixed

People

(Reporter: sarah, Assigned: stransky)

Details

Attachments

(2 files)

Attached file minidump

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.

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.

Component: Untriaged → Widget: Gtk
Product: Firefox → Core
Assignee: nobody → stransky
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Pushed by stransky@redhat.com: https://hg.mozilla.org/integration/autoland/rev/8d31fd9f50c3 [Wayland] Quit if we're missing requested Wayland interface r=emilio
Status: ASSIGNED → RESOLVED
Closed: 9 months ago
Resolution: --- → FIXED
Target Milestone: --- → 131 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: