Bug 470302 – Crash after opening large images

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 470302 - Crash after opening large images


Summary:	Crash after opening large images


Status:	RESOLVED FIXED

Product:	GIMP
Classification:	Other
Component:	General
Version:	2.4.x
Hardware:	Other Linux

Importance:	Normal normal
Target Milestone:	2.4
Assigned To:	GIMP Bugs
QA Contact:	GIMP Bugs

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-08-25 22:06 UTC by Ari Pollak
Modified:	2008-10-30 19:57 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Ari Pollak 2007-08-25 22:06:20 UTC

From Debian bug report http://bugs.debian.org/439489:

I'm getting absolutely reproducible crashes when cropping an image. I have a set of
large TIFF files of 9,4 MB each. When I load two from the set and crop one of them,
Gimp crashes, always at the same point (see below for a stack trace). Cropping with
only one image so far hasn't caused any crashes, but I'll report again if that
changes (as that's the way I'll have to work as long as this bug occurs).

Starting program: /usr/bin/gimp 
[Thread debugging using libthread_db enabled]
[New Thread -1220245840 (LWP 5815)]

(gimp:5815): Gtk-WARNING **: Debug: missing action debug-menu

Program received signal SIGSEGV, Segmentation fault.

+ Trace 157904

Thread NaN (LWP 5815)

#0 render_image_tile_fault_one_row
at /build/buildd/gimp-2.4.0~rc1/./app/display/gimpdisplayshell-render.c line 935
#1 render_image_rgb_a
at /build/buildd/gimp-2.4.0~rc1/./app/display/gimpdisplayshell-render.c line 851
#2 gimp_display_shell_render
at /build/buildd/gimp-2.4.0~rc1/./app/display/gimpdisplayshell-render.c line 264
#3 gimp_display_shell_draw_area
at /build/buildd/gimp-2.4.0~rc1/./app/display/gimpdisplayshell-draw.c line 574
#4 gimp_display_shell_canvas_expose
at /build/buildd/gimp-2.4.0~rc1/./app/display/gimpdisplayshell-callbacks.c line 421
#5 _gtk_marshal_BOOLEAN__BOXED
at /tmp/buildd/gtk+2.0-2.10.13/gtk/gtkmarshalers.c line 84
#6 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#7 ??
from /usr/lib/libgobject-2.0.so.0
#8 ??
#9 ??
#10 ??
#11 ??
#12 ??
#13 ??
from /usr/lib/libcairo.so.2
#14 ??
#15 ??
from /usr/lib/libcairo.so.2
#16 ??
#17 ??
#18 ??
#19 ??
#20 ??
#21 ??

Comment 1 Martin Nordholts 2007-08-26 12:47:24 UTC

Im am unable to reproduce on latest SVN, is the original reporter able to?

Comment 2 Ari Pollak 2007-08-27 03:43:52 UTC

I could reproduce the bug on 2.4.0rc1 and can no longer reproduce it in SVN, so I guess it's fixed. For reference, here are easy steps to reproduce under rc1:
1. Start gimp, set tile cache to 64 MB if it's not already set
2. Create a new image with resolution of 3500x3500
3. Crash

Comment 3 Martin Nordholts 2007-08-27 06:51:01 UTC

I was also able to reproduce it with those steps on RC1, but not on trunk, so this appears to be fixed in trunk. This bug seems not to be a division by zero issue, i.e. it does not look like a duplicate of bug #469785, but it was likely fixed in one of Øyvind's cleanup/fix commits that has taken place after RC1.