GNOME Bugzilla – Bug 324302
jpeg.exe consumes unlimited memory reading attached .jpg
Last modified: 2008-01-15 13:03:26 UTC
Steps to reproduce: 1. Open the attached file jpeg.exe eventually fails to open the file and Gimp asks to be shut down. Stack trace: Other information: I will attach an image causing the problem when I figure out how.
Created attachment 56086 [details] image which is test case for the bug
Created attachment 56087 [details] another test case Both attachments can be opened successfully by several other programs (ImageMagick, Picasa 2, Microsoft Photo Editor, Mozilla Firefox and MS Explorer preview)
Looks like a broken exif maker note. Both those images have been touched by picasa. Can you provide an image directly off your camera so we can determine if your camera is outputing a maker note that libexif can't handle, or if it is picasa that is corrupting things.
I'm pretty sure Picasa has changed it. The original of one of the attachments opens fine in Gimp. You can find at http://home.comcast.net/~metopsy/P3020182.JPG , since it is too big for a bugzilla attachment.
Thanks. Please report a bug to the Picasa people that they are corrupting EXIF data in images. Regardless, GIMP should behave more gracefully with invalid data, so I'm going to leave this bug open until a workaround is in place.
This looks very similar to the previous bug report related to Picasa: bug #166248. It looks like Picasa 2 has several problems with EXIF blocks. However, there are several versions of Picasa 2 (different builds) and the latest ones are supposed to have less bugs. You may want to try downloading a new copy of Picasa 2 while we try to fix the handling of EXIF in the GIMP.
For the records: libexif 0.6.13 still can't handle this type of breakage.
Judging from the symptoms and from the stack trace (exif_set_sshort), this is a duplicate of bug #358117. *** This bug has been marked as a duplicate of 358117 ***