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 592838 - GIMP freezes when picture is resized
GIMP freezes when picture is resized
Status: RESOLVED DUPLICATE of bug 78064
Product: GIMP
Classification: Other
Component: Tools
2.6.7
Other Windows
: Normal major
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2009-08-24 00:23 UTC by Alena Pekna
Modified: 2009-08-30 21:46 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Freezed screen after pressing Scale (89.55 KB, image/gif)
2009-08-24 00:23 UTC, Alena Pekna
Details

Description Alena Pekna 2009-08-24 00:23:53 UTC
Created attachment 141518 [details]
Freezed screen after pressing Scale

Hello,
GIMP freezes with 100% reproducibility when I try to resize a jpeg image (maybe
not only jpeg) in a following way: I open up a jpeg file (approx 4MB in size,
2448 x 3264  Pixels (7.99 MPixels) (3:4))
I click on the scale tool icon, click the image (dialog appears) want to make
the picture very small (400 x ...)
I start to type 4
After first number I notice the chain (maintain ratio) is disconnected, so I
click it, then return back to the number and add two remaining zeros to make it
400. (or any other number (300, 250, probably any number). Then I click Scale,
the picture gets disorted (see attachement) and GIMP stopps responding - or the
process takes infinite time :-( ). 

When I FIRST connect the chain and THEN write the derired number, - then
everything is fine.
Thank you all for your help.
This is my first bug report so I wonder how things (well, rather developers)
work :-)
Alena, Czech Republic
Comment 1 Alena Pekna 2009-08-24 00:34:53 UTC
About my configuration:
notebook HP, 1024MB RAM, Intel cca 2GHz, WinXP SP3,
Computer never experienced a virus, is stable and being run by a play it safe person:-) (all updates in place, NOD32 antivirus, Firefox with adblock and noscript) GIMP was installed a week ago and this has happened from the first time a did the resize this way.
Comment 2 Martin Nordholts 2009-08-24 06:02:02 UTC
Hi and thanks for the bug report! Does this happen also when you scale a newly created 2448 x 3264 image?
Comment 3 Alena Pekna 2009-08-24 07:55:45 UTC
(In reply to comment #2)
> Hi and thanks for the bug report! Does this happen also when you scale a newly
> created 2448 x 3264 image?

For me, yes. I click the scale button, in a dialog I enter number 4, then I click the disconnected chain to connect it, then I continue writing 400 (write "00"), click scale and the program freezes or does something for more then 5minutes now (and GIMP ccreates 50% CPU load).
Thank you for your reply. 
It is possible that the program understands this command strangely and resizis the image into something really big. Maybe it is not completely freezed (maybe he would finish the work in few hours :-)). I do not know. Anyway I do not thing this should happen.
Thank you for your effort!
Comment 4 Michael Schumacher 2009-08-24 08:44:26 UTC
I can reproduce this. The other dimension is set to 200000+, and scaling ot this size is most likely what causes the hang.
Comment 5 Alena Pekna 2009-08-24 09:19:51 UTC
Hello, I'm glad you are able to reproduce that. (Though it is not really a hang because the program is still working) What severity do you assign to it? Do you believe it is worth correcting? Or just people should not do it this way? Thank you! Is there anything more requested from me?
Thank you and have a nice day!
Comment 6 Martin Nordholts 2009-08-24 15:53:04 UTC
Since you ask GIMP to scale the image to 200000+ I would say you will have to take the blame for the freeze, so I'm closing this as NOTABUG.

The interaction with the size entry widgets can certainly be better, but that is well known and should not be handled in the scope of this bug report.
Comment 7 Alena Pekna 2009-08-26 12:08:57 UTC
Hello Martin, thank you for your post, the thing is, that the system looks freezed (though it may not be) and the user does NOT see that the image will be scaled to 200000+ or so. What Michael Schumacher wrote (The dimension is set to 200000+) may be true, but how does a user know? The user sees white freezed windows of GIMP. 
If I wait an hour, I end up with "out of virtual memory"
I am not the only reporting this as a bug (please read developers comments below) It was first noted years ago and a simple message box saying - "Resizing image to 400 x 20000+ may take long! Are you sure?" would solve this. I am not a programmer, but a simple check of dimensions and this question would nicely solve this. 

To sum up developer comments below (for the case you do not want to read it all) :

Sven Neumann   [GIMP developer]
What needs to be done here is to add a simple confirmation dialog just
like the File->New dialog has. The problem to fix here is not the OOM
situation but the fact that you can easily set an unreasonable scaling
factor.


Here are the comments from 2 selected Bugreports:


1.
Bug 21028 -  should warn user about enormous memory consumption  
 Raphaël Quinet   [GIMP developer]      2001-02-09 15:07:55 UTC
The preferences dialog already contains a "Maximum Image Size"
option that triggers a warning if the user tries to create a new
image that is too large.  The same value could be also tested when
the user wants to scale or resize the image.)



2.
Bug 78064 -  Entering large dimensions in Scale Image causes fatal error  
Sven Neumann   [GIMP developer]      2003-11-13 21:36:24 UTC
I am repeating myself but this needs to be catched earlier. There is
not much sense in waiting until we run out of memory. Especially since
due to tile swapping we shouldn't run out of memory at all. Anyway, it
will take a looooooong time until the OOM situation occurs.

What needs to be done here is to add a simple confirmation dialog just
like the File->New dialog has. The problem to fix here is not the OOM
situation but the fact that you can easily set an unreasonable scaling
factor.
Comment 8 Martin Nordholts 2009-08-26 17:43:30 UTC
Ok I see, we'll let's closet this as a duplicate to bug 78064 then.

*** This bug has been marked as a duplicate of bug 78064 ***
Comment 9 Alena Pekna 2009-08-30 21:46:47 UTC
Hello Martin,
thank you for this type of closure, at least - there is a reminder in  bug 78064 and hopefully this problem will be resolved in the future... Have a great day!