1626628 - [KDE/Wayland] Crash in [@ <name omitted> | wl_proxy_create | mozilla::widget::WindowSurfaceWayland::CommitWaylandBuffer ]

Status: RESOLVED WORKSFORME

(Core :: Widget: Gtk, defect, P3)

Description

[Matt Fagnani]

This bug is for crash report bp-ccb4f536-646d-4c22-8efb-258180200401.

Top 8 frames of crashing thread:

0 libwayland-client.so.0 libwayland-client.so.0@0xa4cd 
1 libwayland-client.so.0 libwayland-client.so.0@0xf99f 
2 libwayland-client.so.0 libwayland-client.so.0@0x5f18 
3 libxul.so mozilla::widget::WindowSurfaceWayland::CommitWaylandBuffer widget/gtk/WindowSurfaceWayland.cpp:1128
4 libxul.so mozilla::widget::WindowSurfaceWayland::Commit widget/gtk/WindowSurfaceWayland.cpp:1169
5 libxul.so mozilla::layers::BasicCompositor::EndRemoteDrawing gfx/layers/basic/BasicCompositor.cpp:1169
6 libxul.so mozilla::layers::BasicCompositor::EndFrame gfx/layers/basic/BasicCompositor.cpp:1102
7 libxul.so mozilla::layers::LayerManagerComposite::Render gfx/layers/composite/LayerManagerComposite.cpp:1305

I started Firefox Nightly 76.0a1 (2020-4-1) on Wayland in Plasma 5.18.4 on Wayland in a Fedora 32 KDE Plasma spin installation with KF 5.68.0, Qt 5.13.2. I think I clicked on the Bookmarks menu and looked through them. Firefox showed Not Responding in the title bar. The colours in Firefox faded. Firefox crashed, and the crash reporter appeared. I submitted the crash. A segmentation fault in the Compositor thread in libwayland-client.so.0 in libwayland-client-1.18.0-1.fc32.x86_64 happened which might have been a null pointer dereference since the crash address was 0x0. This crash is the first I've seen with this trace.

Comment 1

[Matt Fagnani]

I'm reassigning this report to Core - Widget:Gtk since it involves Wayland and other reports I've made involving Wayland were assigned to that such as https://bugzilla.mozilla.org/show_bug.cgi?id=1593478 The crash report was reanalyzed due to a debug symbol problem fixed by Gabriele Svelto https://bugzilla.mozilla.org/show_bug.cgi?id=1624171#c11 The top two frames were <name omitted> at src/wayland-util.c:207 and wl_proxy_create at src/wayland-client.c:463 in libwayland-client.so.0 in libwayland-client-1.18.0-1.fc32.x86_64. I've seen similar crashes as these before which Firefox didn't make crash reports for.

Comment 2

[Martin Stránský [:stransky] (ni? me) (PTO, back on Feb 17)]

null pointer crash in KDE/Wayland. Not sure why it happens as waylandSurface is checked before.

Comment 3

[Matt Fagnani]

(In reply to Martin Stránský [:stransky] from comment #2)

null pointer crash in KDE/Wayland. Not sure why it happens as waylandSurface is checked before.

When I've looked at bookmarks or other menus on Nightly 76.0a1 and earlier on Wayland, there's been a delay between when I moved the cursor on a bookmark folder or other item and when its contents appeared and when it was highlighted. Some of the icons on the left sides of the bookmarks were empty. These issues don't happen with Nightly on X. I don't know if that lag in the bookmarks or menus showing up might be related to a Wayland surface being set to null. When the bookmark menu disappeared due to clicking outside of it, the menu surface might have been set to null. Thanks.

Comment 4

[Firefox Bug Husbandry Bot]

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is P3 (Backlog,) indicating it has been triaged, the bug's Severity is being updated to S3 (normal.)

Comment 5

[BugBot [:suhaib / :marco/ :calixte]]

Closing because no crashes reported for 12 weeks.