Bug 767969 – random crash (SIGSEGV)

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 767969 - random crash (SIGSEGV)


Summary:	random crash (SIGSEGV)


Status:	RESOLVED FIXED

Product:	gnome-shell
Classification:	Core
Component:	general
Version:	3.20.x
Hardware:	Other Linux

Importance:	Normal normal
Target Milestone:	---
Assigned To:	gnome-shell-maint
QA Contact:	gnome-shell-maint

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2016-06-23 08:57 UTC by Paul Wise
Modified:	2016-06-23 16:48 UTC

See Also:
GNOME target:	---
GNOME version:	3.19/3.20

Attachments
gdb backtrace of the crash (21.62 KB, text/plain) 2016-06-23 08:57 UTC, Paul Wise		Details
ui/frames: Drop the current grab info on button release (938 bytes, patch) 2016-06-23 13:43 UTC, Rui Matos	committed	Details \| Review

Description Paul Wise 2016-06-23 08:57:46 UTC

Created attachment 330240 [details]
gdb backtrace of the crash

I got a random crash (SIGABRT) in gnome-shell. I am using gnome-shell 3.20.2-3, Xorg and GNOME 3.20 on Debian stretch. If the below gdb backtrace and the attached isn't useful, please close this bug.

Core was generated by `/usr/bin/gnome-shell'.
Program terminated with signal SIGABRT, Aborted.

+ Trace 236383

#0 __GI_raise
at ../sysdeps/unix/sysv/linux/raise.c line 55
#0 __GI_raise
at ../sysdeps/unix/sysv/linux/raise.c line 55
#1 __GI_abort
at abort.c line 89
#2 meta_bug
at core/util.c line 436
#3 get_window
at core/core.c line 58
#4 meta_core_begin_grab_op
at core/core.c line 220
#5 meta_ui_frame_handle_event
at ui/frames.c line 918
#6 meta_ui_frame_handle_event
at ui/frames.c line 1282
#7 meta_ui_frame_handle_event
at ui/frames.c line 1528
#8 meta_window_handle_ungrabbed_event
at core/window.c line 7702
#9 event_callback
at core/events.c line 303
#10 event_callback
at core/events.c line 363
#11 _clutter_event_process_filters
at clutter-event.c line 1802
#12 _clutter_process_event
at clutter-main.c line 2044
#13 _clutter_process_event
at clutter-main.c line 2401
#14 _clutter_process_event
at clutter-main.c line 2561
#15 _clutter_stage_process_queued_events
at clutter-stage.c line 1031
#16 clutter_clock_dispatch
at clutter-master-clock-default.c line 364
#17 clutter_clock_dispatch
at clutter-master-clock-default.c line 561
#18 g_main_context_dispatch
at /build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c line 3154
#19 g_main_context_dispatch
at /build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c line 3769
#20 g_main_context_iterate
at /build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c line 3840
#21 g_main_loop_run
at /build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c line 4034
#22 meta_run
at core/main.c line 537
#23 main
at main.c line 471

Comment 1 Rui Matos 2016-06-23 13:43:26 UTC

Created attachment 330258 [details] [review]
ui/frames: Drop the current grab info on button release

This was added in commit d05b750b8dec3825d286e3ae30c41b41bd6aed98 and
later removed inadvertently in commit
d561b3b18f73a66bcd7947dce7ab1aab9e09965a .

--

Not 100% sure this fixes this crash, but it seems likely since I can't
find any other way for a frame's xwindow to no longer be registered.

Comment 2 Florian Müllner 2016-06-23 13:53:54 UTC

Review of attachment 330258 [details] [review]:

LGTM

Comment 3 Rui Matos 2016-06-23 16:48:43 UTC

I'll close the bug anyway. Please report back if it happens again
after you update to a release that includes this patch.

Attachment 330258 [details] pushed as 1d2bead - ui/frames: Drop the current grab info on button release