Closed Bug 1625849 Opened 4 years ago Closed 3 years ago

Crash in [@ mozalloc_abort | abort | wl_abort | wl_proxy_marshal_array_constructor_versioned | wl_proxy_marshal | gdk_wayland_drag_context_manage_dnd]

Categories

(Core :: Widget: Gtk, defect)

defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: gsvelto, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: crash)

Crash Data

This bug is for crash report bp-932680c7-5223-42a5-a17d-09b380200325.

Top 10 frames of crashing thread:

0 firefox mozalloc_abort /build/firefox-7zdu9Q/firefox-74.0+build3/memory/mozalloc/mozalloc_abort.cpp:33
1 firefox abort /build/firefox-7zdu9Q/firefox-74.0+build3/memory/mozalloc/mozalloc_abort.cpp:82
2 libwayland-client.so.0.3.0 wl_abort ./build/../src/wayland-util.c:417
3 libwayland-client.so.0.3.0 wl_proxy_marshal_array_constructor_versioned ./build/../src/wayland-client.c:744
4 libwayland-client.so.0.3.0 wl_proxy_marshal ./build/../src/wayland-client.c:787
5 libgdk-3.so.0.2404.8 gdk_wayland_drag_context_manage_dnd ../../../../../gdk/wayland/gdkdnd-wayland.c:404
6 libgtk-3.so.0.2404.8 gtk_drag_begin_internal ./debian/build/deb/gtk/../../../../gtk/gtkdnd.c:1834
7 libgtk-3.so.0.2404.8 gtk_drag_begin ./debian/build/deb/gtk/../../../../gtk/gtkdnd.c:2027
8 libxul.so nsDragService::InvokeDragSessionImpl /build/firefox-7zdu9Q/firefox-74.0+build3/widget/gtk/nsDragService.cpp:358
9 libxul.so nsBaseDragService::InvokeDragSession /build/firefox-7zdu9Q/firefox-74.0+build3/widget/nsBaseDragService.cpp:316

This looks like a drag'n'drop-related crash when using Wayland. It's happening on both Ubuntu and Fedora with slightly different signatures.

Blocks: wayland

Looks like something from this function arguments is null:

gdkdnd-wayland.c: gdk_wayland_drag_context_manage_dnd()

wl_data_device_start_drag (gdk_wayland_device_get_data_device (device),
context_wayland->data_source,
gdk_wayland_window_get_wl_surface (toplevel),
context_wayland->dnd_surface,
_gdk_wayland_display_get_serial (display_wayland));

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

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

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

Severity: normal → S3

The severity of these bugs was changed, mistakenly, from normal to S3.

Because these bugs have a priority of --, indicating that they have not been previously triaged, these bugs should be changed to Severity of --.

Severity: S3 → --

Closing because no crashes reported for 12 weeks.

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