gedit crashed with SIGSEGV

Bug #908718 reported by Daniel Winzen on 2011-12-26
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Won't Fix
gedit (Ubuntu)

Bug Description

gedit crashed while loading a very big file about 50MB.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gedit 3.2.5-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-6.12-generic-pae 3.2.0-rc6
Uname: Linux 3.2.0-6-generic-pae i686
ApportVersion: 1.90-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Sun Dec 25 22:51:48 2011
ExecutablePath: /usr/bin/gedit
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
ProcCmdline: gedit /media/07EF-002F/Android/data/$com.MAP.OSM.DEU/map_osm_5.3.0.99/deu/map_osm_5.3.0.99/saarland.12.ydb
 PATH=(custom, no user)
 Segfault happened at: 0x8083816: mov 0x8(%eax),%eax
 PC (0x08083816) ok
 source "0x8(%eax)" (0xaaaaaab2) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gedit
 ?? ()
 ?? ()
 ?? ()
Title: gedit crashed with SIGSEGV
UpgradeStatus: Upgraded to precise on 2011-12-18 (7 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare tape video

visibility: private → public

 scroll_to_cursor (tab=0x92e5828) at gedit-tab.c:956
 ?? ()
 ?? ()

tags: added: apport-failed-retrace
tags: removed: need-i386-retrace
Changed in gedit (Ubuntu):
importance: Undecided → Low
Sebastien Bacher (seb128) wrote :

Thank you for your bug report, does it happen every time you try to open that file? It seems a bit similar to

Could you get a stacktrace using gdb when it happens?

Changed in gedit (Ubuntu):
status: New → Incomplete

Yes, it happens every time I try to open that file or files with the same size. I have to stop gedit manual with gnome-system-monitor after it crashed.
I don't know how to use gdb, so I can't get a stacktrace.

Sebastien Bacher (seb128) wrote :

Could you try to follow and get a valgrind log for the issue?

Changed in gedit (Ubuntu):
status: Incomplete → New

Now I got a valgrind log for the issue.

PS: A few days ago I made an update of gedit, now there is no crash anymore, it just takes about 10 minutes to load the file.

Sebastien Bacher (seb128) wrote :
Download full text (3.8 KiB)

the issue is

"==5940== Invalid write of size 4
==5940== at 0x4B5B5E7: g_nullify_pointer (in /lib/i386-linux-gnu/
==5940== by 0x4AA779A: ??? (in /usr/lib/i386-linux-gnu/
==5940== by 0x4B0FD35: g_datalist_id_set_data_full (in /lib/i386-linux-gnu/
==5940== by 0x4AA78D8: ??? (in /usr/lib/i386-linux-gnu/
==5940== by 0x4061660: ??? (in /usr/lib/
==5940== by 0x80770AD: ??? (in /usr/bin/gedit)
==5940== by 0x4AA8921: g_object_unref (in /usr/lib/i386-linux-gnu/
==5940== by 0x4356A3F: gtk_text_view_set_buffer (in /usr/lib/i386-linux-gnu/
==5940== by 0x435950C: ??? (in /usr/lib/i386-linux-gnu/
==5940== by 0x808C29C: ??? (in /usr/bin/gedit)
==5940== by 0x4AA653B: g_cclosure_marshal_VOID__VOID (in /usr/lib/i386-linux-gnu/
==5940== by 0x4AA39DC: ??? (in /usr/lib/i386-linux-gnu/
==5940== by 0x4AA4EB5: g_closure_invoke (in /usr/lib/i386-linux-gnu/
==5940== by 0x4AB6704: ??? (in /usr/lib/i386-linux-gnu/
==5940== by 0x4ABE0C1: g_signal_emit_valist (in /usr/lib/i386-linux-gnu/
==5940== Address 0xc8d5ebc is 28 bytes inside a block of size 128 free'd
==5940== at 0x402906C: free (in /usr/lib/valgrind/
==5940== by 0x4B32B5A: ??? (in /lib/i386-linux-gnu/
==5940== by 0x4B32CCF: g_free (in /lib/i386-linux-gnu/
==5940== by 0x4B470FA: g_slice_free1 (in /lib/i386-linux-gnu/
==5940== by 0x4AC6401: g_type_free_instance (in /usr/lib/i386-linux-gnu/
==5940== by 0x4AA8A7A: g_object_unref (in /usr/lib/i386-linux-gnu/
==5940== by 0x4079FBC: ??? (in /usr/lib/
==5940== by 0x4B29AF7: g_list_foreach (in /lib/i386-linux-gnu/
==5940== by 0x4B29B41: g_list_free_full (in /lib/i386-linux-gnu/
==5940== by 0x407A87F: ??? (in /usr/lib/
==5940== by 0x4AA8921: g_object_unref (in /usr/lib/i386-linux-gnu/
==5940== by 0x409C637: ??? (in /usr/lib/
==5940== by 0x808C3A8: ??? (in /usr/bin/gedit)
==5940== by 0x4AAA026: g_object_run_dispose (in /usr/lib/i386-linux-gnu/
==5940== by 0x43D4280: gtk_widget_destroy (in /usr/lib/i386-linux-gnu/
==5940== by 0x41805BB: ??? (in /usr/lib/i386-linux-gnu/
==5940== by 0x42F431F: ??? (in /usr/lib/i386-linux-gnu/
==5940== by 0x41D63A6: gtk_container_foreach (in /usr/lib/i386-linux-gnu/
==5940== by 0x41D7754: ??? (in /usr/lib/i386-linux-gnu/
==5940== by 0x42F4B4F: ??? (in /usr/lib/i386-linux-gnu/
==5940== by 0x4AA653B: g_cclosure_marshal_VOID__VOID (in /usr/lib/i386-li...


Sebastien Bacher (seb128) wrote :

or and gedit-dbgsym as well

Now I installed the debug packages and got again a valgrid log.

Sebastien Bacher (seb128) wrote :

thanks, that new log has no similar error though ... could you try again and see if you have some gtk_text_view_set_buffer mention in the log for example?

Now I got a third version of valgrind log.

Changed in gedit (Ubuntu):
status: New → Confirmed
Changed in gedit:
importance: Unknown → Critical
status: Unknown → New
Changed in gedit:
importance: Critical → Wishlist
Changed in gedit:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.