GNOME Bugzilla – Bug 324755
Crash when creating specific image type
Last modified: 2008-01-15 13:03:35 UTC
I am trying to use the GIMP to process photos into a photo of a particular size and dimension. This requires me being very specific about the DPI setting of a new image, which I am to paste the original pictures into. However, when I try to create an image of 6" x 4" with a DPI of 383 (which is what I calculated was required to resize the source image correctly), GIMP will crash. This is very easily repeated on my Windows system. I saw the crash in 2.2.6, and upgraded to 2.2.9 last night, and the crash still occurs - but in 2.2.9 the canvas window actually appeared on the screen before the GIMP crashed. Note - Having tried this on 2.2.9 on Debian Linux - I could not replicate the same crash. On Debian - I have a 64Mb Tile Cache (running in a 128Mb VM), on Windows XP I have a 128 Mb Tile Cache (running on a 1Gb machine). Both are based upon an AMD Sempron.
Your crash could be caused by the warning dialog that is shown if your new image exceeds the "Maximum Image Size" setting. Please try to increase that value in the Preferences. Then report back if that changes anything. Oh, and you should consider to increase your tile cache size on the machine with a gig of RAM.
Hi, Okay - I tried increasing to 256Mb, and recreating the same image - no ball. I also increased my tile cache to 256Mb on the 1 gig box. With a max image size of 512 Mb - still get the same crash. Now unless I am way off here, a 6 x 4 image at 383 DPI, probably with 24 bit + alpha channel is 2304 * 1532 * 4 bytes - 14118912 bytes - around 13.5Mb. Even with a few extra layers of undo and dynamic information, 512Mb should be more than enough - shouldnt it? So I dont expect increasing it beyond this size would help. Another thing that is interesting to note here, is that when gimp crashes, it leaves the script-fu.exe process behind - which I have to kill manually.
Please have a look at bug 314529 - could this be the cause?
Thanks Micheal - I had actually recently installed GAIM, and accepted their version of GTK+. This was definately the cause. I will go check if someone has filed a bug there - and do so if I cant find one - and (this will be pleasant), record the GAIM bug number on bug 314529. *** This bug has been marked as a duplicate of 314529 ***