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 555033 - jpg memory allocation
jpg memory allocation
Status: RESOLVED INVALID
Product: GIMP
Classification: Other
Component: libgimp
2.6.0
Other All
: Normal critical
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2008-10-04 21:05 UTC by Uwe Liebrenz
Modified: 2008-10-04 22:38 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Uwe Liebrenz 2008-10-04 21:05:27 UTC
Please describe the problem:
When opening a jpg image with the dimensions 15000px to 15000px and 8bit depth, gimp should allocate about 215MB. But it consumes round about 1.1GB

Steps to reproduce:
1. open or create a jpg with the dimensions 15000px to 15000px with 8bit depth 
2. save that jpg
3. reopen the jpg


Actual results:
Memory consumtion beyond expected calculation, Depending your RAM no working possible.

Expected results:
lower memory consuption.

Does this happen every time?
yes

Other information:
tracked this problem down to libjpeg62 on Linux or jpeg62.dll on windows. It's also reproduceable in the 2.4.x version of gimp.
Comment 1 Michael Schumacher 2008-10-04 21:07:51 UTC
If you think that this is a problem in libjpeg, why do you report it against GIMP?
Comment 2 Uwe Liebrenz 2008-10-04 21:48:07 UTC
I'm sorry if it is wrong to point to gimp. I thought as an image manipulation program that libjpg62 is a result of the work of the gimp-devs.
Secondly, I believe it is libjpg62 but I could be wrong with that - mybe it's a wrong calculation in Gimp itself?
Thirdly Gimp is the application where I found the problem and can reproduce it ...

Anyway if you have a better place where to file the bug please tell me.
Comment 3 Sven Neumann 2008-10-04 21:51:46 UTC
I think your bug report is based on a misunderstanding and wrong assumptions. If you want us to explain memory usage of GIMP to you, why don't you ask on the mailing-list? The bug-tracker is the wrong place for this.
Comment 4 Uwe Liebrenz 2008-10-04 21:59:16 UTC
I'm sorry if I caused any inconvenience.
But please follow my steps. You will see and have to agree that the memory allocation of gimp is wrong, do you?
Comment 5 Sven Neumann 2008-10-04 22:22:00 UTC
No, I disagree. And I kindly asked you to ask on the mailing-list if you need to have this explained. Perhaps it is sufficient though if you read the last section on http://www.gimp.org/unix/howtos/tile_cache.html
Comment 6 Uwe Liebrenz 2008-10-04 22:38:41 UTC
Ok. I'm pretty sure it has nothing, absolutely nothing, todo with the tile cache but I asked my question on the mailing list. Maybe you can help me what misunderstanding I'm in.
I will leave this report at current resolved invalid state.