GNOME Bugzilla – Bug 589367
gedit crashed with SIGSEGV in IA__g_list_last()
Last modified: 2009-09-01 02:06:38 UTC
this report has been filed here: https://bugs.edge.launchpad.net/ubuntu/+source/gedit/+bug/401934 "Trying to open a python script. It worked one time but crashes on any subsequent attempt." " Same here. I attempted to run after a fresh boot with the same crash. code: quagmire@quagmire-desktop:~$ sudo gedit /etc/pulse/default.pa [sudo] password for quagmire: Segmentation fault (core dumped) quagmire@quagmire-desktop:~$ /code However, it doesn't crash all the time. If I open Text Editor from the Applications - Accessories menu, it works fine. If I open a text file on my desktop, it also works fine. If I copy default.pa from /etc/pulse to Desktop, it still does not open from the desktop. However, if I rename the file from default.pa to simply default (on the desktop), it opens fine. If I rename it back to default.pa, it will again crash. " "#0 0x004235c2 in IA__g_list_last (list=0xaaaaaaaa) at /build/buildd/glib2.0-2.21.4/glib/glist.c:717 No locals.
+ Trace 216572
crash in gdk with 2.27... client side windows issue?
Dubious. Can you reproduce this under valgrind ? Ie G_SLICE=always-malloc valgrind gedit foo
valgrind log available at http://launchpadlibrarian.net/29673804/valgrind-logs-gedit_gtk-dbg.tar.gz
The crash does not happen with files which have not been edited , crash happens only with files that have been edited. Has something to do with restoring the state of the document, and scrolling the document to the last location.
the ubuntu bug has 38 duplicates that seems a frequent crasher
This looks like bug 591434, or at least related to it.
fixed with commit 9f822431970b9744f0184ae2d9e9977f607ffe4e
the commit doesn't fix the issue reopening the bug, similar crash keep being opened on the ubuntu bug tracker using a gtk with this change
Is there a valgrind log for the new crash?
Created attachment 141086 [details] Valgrind log of gedit Attached a valgrind log run with debug symbols for libgtk2.0-0 and gedit installed (Ubuntu karmic alpha). The log was obtained as follows: $ sudo -s -H $ G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log gedit /etc/apt/sources.list (as per https://wiki.ubuntu.com/Valgrind ) When running gedit with valgrind, it did *not* crash. Whereas when running simply $ sudo -s -H $ gedit /etc/apt/sources.list it crashes. I have no experience with Valgrind, so if this is not the expected behaviour, please advice how to proceed with debugging.
Created attachment 141092 [details] valgrind run without G_DEBUG=gc-friendly Just noticed a comment in launchpad regarding the crashing with valgrind. Running without G_DEBUG=gc-friendly crashes gedit with valgrind. Log of following run attached: $ sudo -s -H # G_SLICE=always-malloc valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log gedit /etc/apt/sources.list An additional valgrind log by another user has been posted to the original launchpad bugreport.
428d7bd27bccb4f21d210cefc2024cfb526d398c has some more fixes. Hopefully this fixes it. Anyone that can reproduce this, please verify.
I am going to assume this is fixed. Please reopen if you still see this with 2.17.9+.