GNOME Bugzilla – Bug 726749
Segmentation fault in libglib-2.0.so.0 with glib-2.39.92
Last modified: 2014-03-21 16:32:29 UTC
I'm seeing two apps segfault on shutdown and backtrace points me to glib library, magazine_chain_pop_head function. The apps in question are Totem 3.9.91 and Gedit 3.11.92 Backtraces follow. Totem: Program received signal SIGSEGV, Segmentation fault. 0x00007ffff0a4cc05 in magazine_chain_pop_head (magazine_chunks=<synthetic pointer>) at gslice.c:544 544 gslice.c: No such file or directory. (gdb) bt
+ Trace 233371
Gedit: Program received signal SIGSEGV, Segmentation fault. 0x00007ffff48d1c05 in magazine_chain_pop_head (magazine_chunks=<synthetic pointer>) at gslice.c:544 544 gslice.c: No such file or directory. (gdb) bt
+ Trace 233372
Created attachment 272444 [details] gedit vgdump valgrind --tool=memcheck --leak-check=full --leak-resolution=high --num-callers=20 --log-file=vgdump gedit
Both backtraces have some functions from GtkPopover. So it maybe comes from GTK+ or a misuse of GtkPopover.
what version of GTK+ was this with ?
Bug 726747 might be related to this crash.
glib-2.0 - 2.39.92 atk - 2.11.92 cairo - 1.12.16 pango - 1.36.3 gtk+-3.0 - 3.11.9 gtksourceview-3.0 - 3.11.91 gedit - 3.11.92 totem - 3.11.91
*** Bug 726673 has been marked as a duplicate of this bug. ***
Created attachment 272567 [details] [review] a11y: Remove weak reference when updating a GtkPopoverAccessible relative-to widget Otherwise the weak reference is left dangling, which later causes issues at the time of destroying that widget.
Review of attachment 272567 [details] [review]: looks good to me.
*** Bug 726805 has been marked as a duplicate of this bug. ***
*** Bug 726747 has been marked as a duplicate of this bug. ***
A hard code freeze break was approved for this one. Pushed to master. Attachment 272567 [details] pushed as 0e7884f - a11y: Remove weak reference when updating a GtkPopoverAccessible relative-to widget