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 348260 - Gthumb makes the system hang trying to open very high resolution images
Gthumb makes the system hang trying to open very high resolution images
Status: RESOLVED DUPLICATE of bug 80925
Product: gthumb
Classification: Other
Component: general
Other All
: Normal critical
: ---
Assigned To: Paolo Bacchilega
Paolo Bacchilega
Depends on:
Reported: 2006-07-21 15:42 UTC by Bordiga Giacomo
Modified: 2008-04-11 14:48 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Bordiga Giacomo 2006-07-21 15:42:21 UTC
Steps to reproduce:
1. Open the image

Stack trace:

Other information:
Gthumb while trying to open a very high resolution image, allocates so much memory that the whole system hangs.
The image i tested is 20416 x 28064, bmp (60MB), jpeg (33MB) and png (3.3MB).
I got this problem when nautilus asked gthumb to thumbnail the png image.
Comment 1 Sergej Kotliar 2006-07-21 18:01:30 UTC
Nautilus should normally thumbnail images itself... unless you have some kind of special circumstance?
Does this happen when opening it in gthumb too? I mean, actually opening it from within gthumb.

Otherwise, this seems like a duplicate of 134544...
Comment 2 Bordiga Giacomo 2006-07-21 22:27:27 UTC
Sorry, i was pretty sure that nautilus used gthumb to make thumbnails of images. I was wrong. I double checked and is the nautilus process to take all the memory.
However opening the images in gthumb (and of course opening the folder containing the images), creates the same effect. Gthumb eats up all the memory and makes the system hang.
Comment 3 marty leisner 2006-08-23 00:02:26 UTC
When going into the print dialogure, and printing a number of large images (3-8 Mbyte), the memory behavior is terrible.

I have 1 gig physical + virtual, and printing about a dozen images in one shot blows out of memory...

Just as an experiment, I print-previewed 12 images (4 per page) of smaller
images (< 1 Meg/image) -- RSS went up to 200 Mbyte.

Comment 4 Björn Lindqvist 2007-04-04 23:59:48 UTC
This is because a GdkPixbuf is used to store the image. GdkPixbuf uses 3 bytes per pixel to store images in memory. So a 20416 x 28064 would need 1.6 GB RAM which obviously, is way to much to handle. EOG suffers from the same problem for the same reason.
Comment 5 Michael Chudobiak 2008-04-11 14:48:28 UTC
No, this is because the gtk+ scaling functions blow up at high scale factors. Dupe of bug 80925.

- Mike

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