Open
Bug 1795648
Opened 2 years ago
Updated 2 years ago
Crash in [@ wl_proxy_get_user_data | data_device_enter]
Categories
(Core :: Widget: Gtk, defect, P3)
Tracking
()
NEW
People
(Reporter: gsvelto, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: crash)
Crash Data
Crash report: https://crash-stats.mozilla.org/report/index/55feef82-a2de-4bae-a1d3-ff85c0221013
Reason: SIGSEGV / SEGV_MAPERR
Top 10 frames of crashing thread:
0 libwayland-client.so.0 wl_proxy_get_user_data /build/gnome-3-38-2004-sdk/parts/wayland/build/src/wayland-client.c:2025
1 libgdk-3.so.0 data_device_enter /build/gnome-3-38-2004-sdk/parts/gtk/src/gdk/wayland/gdkdevice-wayland.c:1177
2 libffi.so.7 ffi_call_unix64
3 libffi.so.7 ffi_call_int
4 libwayland-client.so.0 wl_closure_invoke /build/gnome-3-38-2004-sdk/parts/wayland/build/src/connection.c:1014
5 libwayland-client.so.0 dispatch_event /build/gnome-3-38-2004-sdk/parts/wayland/build/src/wayland-client.c:1430
6 libwayland-client.so.0 dispatch_queue /build/gnome-3-38-2004-sdk/parts/wayland/build/src/wayland-client.c:1576
7 libwayland-client.so.0 wl_display_dispatch_queue_pending /build/gnome-3-38-2004-sdk/parts/wayland/build/src/wayland-client.c:1818
8 libwayland-client.so.0 wl_display_dispatch_pending /build/gnome-3-38-2004-sdk/parts/wayland/build/src/wayland-client.c:1881
9 libgdk-3.so.0 _gdk_wayland_display_queue_events /build/gnome-3-38-2004-sdk/parts/gtk/src/gdk/wayland/gdkeventsource.c:201
This seems to be drag & drop related, some comments from the crashes:
Was dragging a new bookmark into a folder and firefox crashed outa nowhere
Tried to separate one tab from the rest when it crashed.
I was just trying to drag my imported bookmarks around
crashed dragging a URL (via the lock icon) to a bookmark toolbar folder to add a bookmark
Comment 1•2 years ago
|
||
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
You need to log in
before you can comment on or make changes to this bug.
Description
•