Crash when doing a replace all: gedit crashed with SIGSEGV in gtk_text_iter_set_offset()

[Huygens]

Binary package hint: gedit

I had just exported my WordPress database as an SQL file. I opened it with gedit and used the replace all feature. I wanted to change the name of the table. WordPress default prefix is wp_ and I decided to change it to wp27_. It took some time, then gedit became darker (so not responding) and then disappeared (crashed).
I opened the file with vim, and in a second 117 substitions were done, no crash.

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/gedit
Package: gedit 2.26.0-0ubuntu3
ProcCmdline: gedit /home/username/Downloads/magicalw(2).sql
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gedit
StacktraceTop:
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 gtk_text_iter_set_offset ()
 ?? () from /usr/lib/libgtksourceview-2.0.so.0
 ?? () from /usr/lib/libgtksourceview-2.0.so.0
Title: gedit crashed with SIGSEGV in gtk_text_iter_set_offset()
Uname: Linux 2.6.28-11-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare users

[Huygens (huygens-25)]

Sorry, I had to remove the core dump as it contains information from the file I opened. And there are e-mails and other stuff that I do not want to publish.
In case you want the core dump, you will have to request it directly to me, and I will try to "clean" it before sending it.

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

[Sebastien Bacher (seb128)]

the apport bugs are private by default and nobody has access to the coredump until retracing, the retracer provides a debug stacktrace and clean the coredump while doing so, you broke the retracing by cleaning the bug yourself though so it would be nice if you could get a stacktrace and add it there

[Huygens (huygens-25)]

The next time I'm home and using my computer, I will try to reproduce the bug and generate a stack trace that is usable for you and that does not contain sensitive information.
One note though, if you have a wordpress blog, try to export the entire wordpress database (only the wordpress related table). Then from the SQL file, open it with gedit and try to replace the wordpress table prefix with something else using replace all.

[Huygens (huygens-25)]

Hello Sebastien,
You can find attached here the backtrace of gedit during the crash.
About the retracer, do you mean that it is a launchpad feature that will analyse the coredumped, create a backtrace from it, delete the coredumped and then will make public the bug report? That's a great feature!

[Huygens (huygens-25)]

I forgot to mention that gedit has been updated but I still have the bug, here is my current version of gedit: 2.26.1-0ubuntu1

[Sebastien Bacher (seb128)]

could you install the gtk and gtksourceview debug packages and get a new stacktrace?

[Sebastien Bacher (seb128)]

> do you mean that it is a launchpad feature that will analyse the coredumped, create a backtrace from it, delete the coredumped and then will make public the bug report? That's a great feature!

right, the making public part is not automatic though, somebody has to check that the stacktrace has no private informations

[Huygens (huygens-25)]

Hello Sebastien,
I have installed the following package:
sudo apt-get install libgtk2.0-0-dbgsym=2.16.1-0ubuntu2
sudo apt-get install libgtksourceview2.0-0-dbgsym=2.6.1-0ubuntu1

Then I have run once more the test, you can find attached the stacktrace.
NB: gedit crashed once more, I have the final version of Ubuntu 9.04 and gedit is still version: 2.26.1-0ubuntu1

[Sebastien Bacher (seb128)]

Could somebody having the issue send the bug the to the people writting the software (https://wiki.ubuntu.com/Bugs/Upstream/GNOME)?

[Huygens (huygens-25)]

Adding a reference to the upstream bug in Gnome Bugzilla system

[Sebastien Bacher (seb128)]

Thank you for sending the bug to GNOME

[schwascore (josh-ya4)]

I have the same issue, also with a WordPress database dump trying to do the same type of prefix replacement.

[Huygens (huygens-25)]

Just for information, here is my last comment on the bugzilla tracker:

I have perform the test with the same data on 3 other platforms since the bug report:
 1. - latest Ubuntu Karmic Koala (future 9.10) 32bit
 2. - latest Ubuntu 9.04 32bit
 3. - latest Ubuntu 8.04.2 LTS 32bit

The crash has been reproduced with platform 1 and 2. However, with platform 3, there was no crash (though the CPU was as high as 100% for several seconds). On platform 3, gedit is in version 2.22.3.

Just as a reminder, the platform used for the initial bug report was Ubuntu 9.04 64bit.

[Raymond Hill (rhill)]

Just got the same crash. In my case, I was opening two huge (~7MB each) SQL dumps simultaneously (I wanted to perform a diff). I didn't interact at all with gedit, as far as I can tell, the SQL dumps where being opened/parsed by gedit when the crash occurred.

[Chris Wilson (notgary-deactivatedaccount)]

Is this bug still affecting people with Gedit 3.3.x?

[Fabio Marconi (fabiomarconi)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

[Jaromir Obr (jaromir-obr)]

It should be fixed in gedit 3.10, see https://bugzilla.gnome.org/show_bug.cgi?id=584803#c7
This version is a part of Ubuntu 14.04.