Closed Bug 1611759 Opened 9 months ago Closed 6 months ago

Crash in [@ mozalloc_abort | abort | wl_array_copy | wl_proxy_marshal_array_constructor_versioned | wl_proxy_marshal | gdk_wayland_device_pad_set_feedback]

Categories

(Core :: Widget: Gtk, defect)

Unspecified
Linux
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox74 --- wontfix

People

(Reporter: gsvelto, Unassigned)

Details

(Keywords: crash)

Crash Data

This bug is for crash report bp-baee865c-3bf1-424c-b5dd-ca2d90200125.

Top 10 frames of crashing thread:

0 firefox-bin mozalloc_abort memory/mozalloc/mozalloc_abort.cpp:33
1 firefox-bin abort memory/mozalloc/mozalloc_abort.cpp:82
2 libwayland-client.so.0.3.0 wl_array_copy 
3 libwayland-client.so.0.3.0 wl_proxy_marshal_array_constructor_versioned 
4 libwayland-client.so.0.3.0 wl_proxy_marshal 
5 libgdk-3.so.0.2406.7 gdk_wayland_device_pad_set_feedback 
6 libgtk-3.so.0.2406.7 gtk_drag_set_icon_widget 
7 libgtk-3.so.0.2406.7 gtk_drag_begin 
8 libxul.so nsDragService::InvokeDragSessionImpl widget/gtk/nsDragService.cpp:358
9 libxul.so nsBaseDragService::InvokeDragSession widget/nsBaseDragService.cpp:316

This seems to be happening only on Arch Linux w/ Wayland unless the signature is different on other distros. It seems like we're hitting an assertion in the Wayland code when starting a drag'n'drop operation. Unfortunately we don't have line-numbers for Arch system libraries so it's hard to guess where this is actually happening.

Closing because no crashes reported for 12 weeks.

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