GIMP crashes when trying to resize an image.

Bug #135650 reported by C.Kontros
This bug report is a duplicate of:  Bug #131564: crashes when using the small theme. Edit Remove
6
Affects Status Importance Assigned to Milestone
gimp (Ubuntu)
Incomplete
Medium
Unassigned
ubuntulooks (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: gimp

GIMP is crashing for me on multiple Gutsy machines when resizing a image.

Heres a pastebin of what happens when launched through the cli. http://paste.ubuntu-nl.org/35583

A workaround was suggested online. "G_SLICE=always-malloc gimp" to launch GIMP doesn't exhibit the problem.

C.Kontros (coryisatm)
description: updated
Changed in gimp:
importance: Undecided → Medium
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in gimp:
status: New → Incomplete
Revision history for this message
Sebastien Bacher (seb128) wrote :

Could you try to get a valgrind log for the crash (you can follow the instructions on https://wiki.ubuntu.com/Valgrind)?

Revision history for this message
Sebastien Bacher (seb128) wrote :

could you describe the actions you are doing to trigger the bug?

Revision history for this message
C.Kontros (coryisatm) wrote :

Valgrind log attached.

Revision history for this message
Sebastien Bacher (seb128) wrote :

the log seems to be truncated and has no error, did you get the crash during this run?

Revision history for this message
C.Kontros (coryisatm) wrote :

Sebastien Bacher: "the log seems to be truncated and has no error, did you get the crash during this run?"

No. That was the output of the log. I'll do another. Like I mentioned on IRC, I couldn't get it to crash launching it with:

"G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log gimp"

It went VERY slow that was it. I can make it crash if I create a new image or resize _ANYTHING_. Canvas, layer or image. This happens when launching it from the menu or via CLI.

Attached is another log where things work other than being slow. There's a difference somewhere. I just can't track it down. ion_ on #ubuntu-devel is having this same issue.

Revision history for this message
Sebastien Bacher (seb128) wrote :

the log has still no error

Revision history for this message
Johan Kiviniemi (ion) wrote :

Almost all dialogs crash without G_SLICE=always-malloc here.

I’ve been fighting with gimp’s internal functionality that catches crashes and prints stack traces. I just can’t seem to turn it off. gimp --stack-trace-mode=never doesn’t seem to work.

Because of that, apport doesn’t detect the crashes and using gdb is difficult.

I haven’t tried to valgrind gimp yet, but i’d guess gimp’s crash catching hinders even its reports.

(Since Ubuntu is using apport, perhaps the crash catching functionality should be turned off by default.)

Revision history for this message
Johan Kiviniemi (ion) wrote :

I reported bug #136439 about the --stack-trace-mode problem.

Revision history for this message
Johan Kiviniemi (ion) wrote :

Here’s a valgrind report. It took a full fifteen minutes just to get gimp’s main window opened in a valgrind session. ;-)

This seems to be the relevant part:
==939== Invalid free() / delete / delete[]
==939== at 0x402137F: free (vg_replace_malloc.c:233)
==939== by 0x47948C0: g_free (in /usr/lib/libglib-2.0.so.0.1400.0)
==939== by 0x602EBC5: option_menu_get_props (in /usr/lib/gtk-2.0/2.10.0/engines/libubuntulooks.so)

The problem seems to be in the ubuntulooks theme engine. When i switch to another theme engine (even clearlooks, of which ubuntulooks is a fork IIRC), gimp doesn’t crash anymore.

If i start gimp with another theme engine and choose “New image”, it works. If i then switch back to the Human theme while gimp is still running and choose “New image” again, it crashes.

Revision history for this message
Johan Kiviniemi (ion) wrote :

Here’s a transcript of a gdb session in ubuntulooks’ option_menu_get_props.

Revision history for this message
C.Kontros (coryisatm) wrote :

Wow. I can confirm changing themes fixes the issue as well.

Revision history for this message
Sebastien Bacher (seb128) wrote :

could you install gtk2-engines-ubuntulooks-dbgsym libgtk2.0-0-dbgsym and get a new valgrind log?

Revision history for this message
Sebastien Bacher (seb128) wrote :

libglib2.0-0-dbg would also be useful

Revision history for this message
Johan Kiviniemi (ion) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

could you also install the glib and pango debug packages? That's not clear that's an ubuntulooks issue

Revision history for this message
Sebastien Bacher (seb128) wrote :

Do you use the "small" theme? Looks like a duplicate of bug #131564

Revision history for this message
C.Kontros (coryisatm) wrote :

Yeah. For me, these 2 issues look to be centered around the use of the small theme.

Revision history for this message
stopsatgreen (p-gasston) wrote :

I can confirm that these issues go away when using the Default theme.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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