Closed Bug 1791355 Opened 3 years ago Closed 3 years ago

Crash in [@ nsWindow::WaylandStartVsync]

Categories

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

Unspecified
Linux
defect

Tracking

()

RESOLVED DUPLICATE of bug 1791977

People

(Reporter: gsvelto, Unassigned)

References

Details

(Keywords: crash)

Crash Data

Crash report: https://crash-stats.mozilla.org/report/index/6c96c8f8-645e-405d-b1a6-d50410220916

Reason: SIGSEGV / SEGV_MAPERR

Top 10 frames of crashing thread:

0 libxul.so nsWindow::WaylandStartVsync widget/gtk/nsWindow.cpp:6395
1 libxul.so nsWindow::ResumeCompositorImpl widget/gtk/nsWindow.cpp:6375
2 libxul.so nsWindow::ConfigureCompositor const widget/gtk/nsWindow.cpp:5534
3 libxul.so moz_container_wayland_frame_callback_handler widget/gtk/MozContainerWayland.cpp:306
4 libffi.so.8 ffi_call_unix64 
5 libffi.so.8 ffi_call_int.lto_priv.0 
6 libwayland-client.so.0 wl_closure_invoke.constprop.0 /usr/src/debug/wayland-1.21.0-1.fc37.x86_64/src/connection.c:1025
7 libwayland-client.so.0 dispatch_event.isra.0 /usr/src/debug/wayland-1.21.0-1.fc37.x86_64/src/wayland-client.c:1595
8 libwayland-client.so.0 wl_display_dispatch_queue_pending /usr/src/debug/wayland-1.21.0-1.fc37.x86_64/src/wayland-client.c:1983
9 libgdk-3.so.0 _gdk_wayland_display_queue_events /usr/src/debug/gtk3-3.24.34-2.fc37.x86_64/gdk/wayland/gdkeventsource.c:201

This appears to be a NULL pointer access to whatever was returned from AsGtkCompositorWidget(). mCompositorWidgetDelegate should never be NULL given the assertion which is right above.

I wonder if mCompositorWidgetDelegate is something like CompositorWidgetChild or so.

Flags: needinfo?(stransky)
Flags: needinfo?(stransky)
Priority: -- → P3
Flags: needinfo?(stransky)

Let's see if we get any assert from Bug 1791752.

Flags: needinfo?(stransky)

Since the crash volume is low (less than 5 per week), the severity is downgraded to S3. Feel free to change it back if you think the bug is still critical.

For more information, please visit auto_nag documentation.

Severity: S2 → S3

Already fixed by Bug 1791977.

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.