GNOME Bugzilla – Bug 558170
Gimp crashes when opening several high res Jpegs.
Last modified: 2008-11-22 00:12:14 UTC
Steps to reproduce: 1. Create a letter size 300 Dpi full color image, paint(do some editing) a little and save it in jpeg format. 2. Repeat the process like 4 or 5 times and name them like lets say Image1.jpg, Image2.jpg, etc. 3. Open the first one and do some more editing (paint a little with the brush) and save it then open another and do the same and continue with the others. If the program has not crashed by now just keep repeating this last step (number 3) until the program crashes. Stack trace: Other information: I tried this in Windows XP Pro and in Windows 2000 (in two completely different computers) and it does it on both. Also I didn't notice this with the other image formats, only with .jpegs and it seems to happen with large resolution .jpegs that's why when I did the test I used 300 Dpi letter size. I also noticed that without doing a bit of editing (painting) it doesn't cause the crash (or maybe it causes it after opening many, many files, I tried it for a while and it didn't crash) I have not tested it on Linux. It doesn't happen with Gimp 2.4.7, it happens with Gimp 2.6.0 or Gimp 2.6.1. This seems to happen with large resolution Jpegs. I've noticed that when I was using some 300 Dpi Jpegs the program started to crash and I decided to try to see if I could narrow it down a little and find what was causing the crash and I know that it may not be as specific as It could be but I was able to use the procedure above and reproduce the error on both computers fairly easily and frequently. I did not have the problem with any version of Gimp previous to 2.6.0.
Hi and thanks for the bug report! Can you reproduce it by editing the same image a lot rather than many images a little? Can you reproduce it on Linux?
Yes, I was able to reproduce the bug by using only one picture. I mean I created one letter size 300 Dpi Image and painted a little in it with a blurred large brush, then I saved and closed it and when I opened it again Gimp crashed on the first try. I opened Gimp again, did the same and it crashed on the sixth attempt to open it. Every time I opened it I painted a little with a large blurred brush. I couldn't check the error in Linux because I have OpenSuse Linux 10.3 and I have a problem that doesn't allow me to install glib2-2.16* and without that I cannot install Gimp 2.6.1. I only have Gimp 2.4.6 in my Suse 10.3 machine. If I install glib2-2.16* a lot of programs stop working including Adobe Acrobat reader, the Yast manager itself and many others, when I run them from the command line I can see that many seem to have a problem not finding this library: libglib-2.0.so.0 which glib2-2.14* provides but glib2-2.16* doesn't. I tried to install the libglib-2.0.so.0 library alone to see if that solved the problem but when I tried it asked for a couple of old dependencies that I couldn't find anywhere on the net so I had to go to the command line and force deinstall of the glib2-2.16* library with the rpm manager and then using that I reinstalled glib2-2.14* and Yast and the other software started to work again. I'm not shure if glib2-2.16* can be installed in OpenSuse Linux 10.3 successfully. If you or any of your friends know how to solve this (I couldn't find any posts about this problem on the web) then I'll be able to answer your other question soon. At the moment I'm downloading the Fedora 9 DVD .iso to install it in my Suse 10.3 Machine (my third computer also completely different) so when that's done I may be able to answer that other question but that will take a few days.
Well you can compile and install GLib in a separate prefix like /opt/glib. That way it will not conflict with anything on your system. There's no hurry though. Setting to NEEDINFO as we either need a stack trace from the Windows crash or a way to reproduce it on Linux (I don't seem to be able to).
The problem was related to the Gimp bug of crashing when displaying image preview while opening a file which was corrected in version 2.6.2, that's why it happened far more often when using high resolution images because higher resolution images take longer to display their preview so it was more probable to run into this bug. When I downloaded and installed Gimp version 2.6.2 it disappeared completely. I have been using it for a little while now and the problem has not returned. Thanks for your help.
Thanks for getting back to us. Marking as a duplicate ... *** This bug has been marked as a duplicate of 555246 ***