Open
Bug 2035754
Opened 6 months ago
Updated 1 month ago
Crash in [@ mozilla::widget::WlLogHandler_InvalidSurfaceFrame]
Categories
(Core :: Widget: Gtk, defect)
Core
Widget: Gtk
Tracking
()
NEW
People
(Reporter: gsvelto, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: crash, Whiteboard: gtk-severity-sweep-2026-10)
Crash Data
Crash report: https://crash-stats.mozilla.org/report/index/873a2257-b295-4246-8f06-20d660260425
MOZ_CRASH Reason:
(kde) wl_display#1: error 1: invalid arguments for wl_surface#242.frame
Proxy: WP:E WP:CA WP:CPCA
Top 10 frames:
0 libxul.so MOZ_CrashSequence(void*, long) /usr/src/debug/firefox-nightly/mozilla-central/obj/dist/include/mozilla/Assertions.h:235
0 libxul.so MOZ_Crash(char const*, int, char const*) /usr/src/debug/firefox-nightly/mozilla-central/obj/dist/include/mozilla/Assertions.h:373
0 libxul.so mozilla::widget::WlLogHandler_InvalidSurfaceFrame(char const*) /usr/src/debug/firefox-nightly/mozilla-central/widget/gtk/nsWaylandDisplay.cpp:952
1 libxul.so mozilla::widget::WlLogHandler(char const*, __va_list_tag*) /usr/src/debug/firefox-nightly/mozilla-central/widget/gtk/nsWaylandDisplay.cpp:1047
2 libwayland-client.so.0 wl_log /usr/src/debug/wayland/wayland-1.24.0/src/wayland-util.c:463
3 libwayland-client.so.0 display_handle_error /usr/src/debug/wayland/wayland-1.24.0/src/wayland-client.c:1101
4 libffi.so.8 ffi_call_unix64 /usr/src/debug/libffi/libffi-3.5.2/src/x86/unix64.S:104
5 libffi.so.8 ffi_call_int /usr/src/debug/libffi/libffi-3.5.2/src/x86/ffi64.c:676
6 libffi.so.8 ffi_call /usr/src/debug/libffi/libffi-3.5.2/src/x86/ffi64.c:713
7 libwayland-client.so.0 wl_closure_invoke /usr/src/debug/wayland/wayland-1.24.0/src/connection.c:1241
Few crashes, all coming from nightly users with AMD GPUs. One user in particular represents three crash reports out of four. It looks like a bug that might be specific to this AMD setup. This is one of the more specific crash signatures that originated from the changes in bug 1996093.
Updated•1 month ago
|
Severity: -- → S3
Whiteboard: gtk-severity-sweep-2026-10
You need to log in
before you can comment on or make changes to this bug.
Description
•