I believe a found a bug in image magick 6.3.5
Apparently Adobe Photoshop Elements 4.0 (On Mac) places some extra comment
blocks in it's jpeg files.
When I attempt to "identify" the file, identify crashes with this error message
# identify adobe_bad_comment.jpg
identify in realloc(): warning: junk pointer, too high to make sense
identify in free(): warning: junk pointer, too high to make sense
identify: unable to allocate string `begin="" id="W5M0MpCehiHzreSzNTczkc9d"'.
After I run "jpegtran -copy none" on the file, "identify" has no problems with
it.
# jpegtran -copy none adobe_bad_comment.jpg > adobe_cleaned.jpg
# identify adobe_cleaned.jpg
adobe_cleaned.jpg JPEG 743x557 743x557+0+0 DirectClass 8-bit 106.908kb
Here is the bad commented image:
http://pic1.picturetrail.com/VOL1151/59 ... omment.jpg
Here is the no commentes image
http://pic1.picturetrail.com/VOL1151/59 ... leaned.jpg
Will you be able to place a fix for this in 6.3.5-1?
This bug is not present in 6.3.3, FYI.
TIA,
-daniel
-- System info --
FreeBSD [deleted] 6.1-STABLE FreeBSD 6.1-STABLE #1: Thu Jun 15 14:41:29 PDT 2006 [deleted]
:/usr/obj/usr/src/sys/WWWv2 amd64
# identify -version
Version: ImageMagick 6.3.5 07/06/07 Q16 http://www.imagemagick.org
Copyright: Copyright (C) 1999-2007 ImageMagick Studio LLC
Adobe Elements Jpeg files and bad comments, crash.
Re: Adobe Elements Jpeg files and bad comments, crash.
6.3.5 parses the XMP profile. Apparently its tickling a bug in the XML parser although identifying your image under Fedora Linux seems to work fine. Will investigate further sometime this week.
Re: Adobe Elements Jpeg files and bad comments, crash.
If there is any information I can get you, please let me know.
Thank you,
-daniel
Thank you,
-daniel
Re: Adobe Elements Jpeg files and bad comments, crash.
Grab ImageMagick 6.3.5-1 from ftp://magick.imagemagick.org/pub/ImageMagick/beta in about an hour (its building now). See if the patch to magick./xml-tree.c fixed the problem.
Re: Adobe Elements Jpeg files and bad comments, crash.
We were not able to reproduce this error with Image-Magick 6.3.5-1 beta.
Thank you for the bug fix!!!
-daniel
Thank you for the bug fix!!!
-daniel