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 380028 - Large TIFF causes uncaught Out of Memory
Large TIFF causes uncaught Out of Memory
Status: RESOLVED DUPLICATE of bug 434025
Product: GIMP
Classification: Other
Component: General
2.3.x
Other All
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2006-11-28 05:41 UTC by Dave Jarvis
Modified: 2008-01-15 14:10 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Dave Jarvis 2006-11-28 05:41:37 UTC 
Steps to reproduce:
1. Download (403800956 bytes): http://imgsrc.hubblesite.org/hu/db/2006/01/images/a/formats/full_tif.tif
2. Load TIFF into GIMP
3. Crash


Stack trace:


Other information:
The image is a TIFF of the Orion Nebula from NASA. It is 18000x18000 pixels. I didn't expect the GIMP to load it (give my computer has only 1 GB of memory), but I didn't expect the GIMP to disappear.
Comment 1 Sven Neumann 2006-11-28 16:00:52 UTC 
What did crash? GIMP or the TIFF plug-in?
Comment 2 Dave Jarvis 2006-11-28 20:13:09 UTC 
How can I tell the difference?

I was able to use the ImageMagick "convert" tool to manipulate the image, which I believe implies libtiff is functioning correctly.
Comment 3 Michael Schumacher 2007-01-14 14:57:10 UTC 
The difference is:

- if only the plug-in does crash, you can still continue to use GIMP
Comment 4 Sven Neumann 2007-05-07 14:02:13 UTC 

*** This bug has been marked as a duplicate of 434025 ***