Post any defects you find in the released or beta versions of the ImageMagick software here. Include the ImageMagick version, OS, and any command-line required to reproduce the problem. Got a patch for a bug? Post it here.
I'm using ImageMagick CLI version 7.0.7.24 in Windows, now I want to upgrade the version to 7.0.8.16 - the lastest version but there are some issues with the new one. When using new version and try to convert a jpg file to bmp file, I got an error log like below:
convert.exe: CorruptImageProfile `xmp' @ warning/profile.c/SetImageProfileInternal/1746.
convert.exe: memory allocation failed `D:\1e7f62069f7440c983950023090c0a3a.jpg' @ error/jpeg.c/ReadProfile/803.
convert.exe: Improper call to JPEG library in state 201 `D:\1e7f62069f7440c983950023090c0a3a.jpg' @ error/jpeg.c/JPEGErrorHandler/333.
But in version 7.0.7.24, there is no error and converted file is ok. My command is just:
v7.0.7-28 also converts with no problem. Exiftool says the file has a massive document history, and perhaps more recent IM has a bug that doesn't allocate enough memory.
It's trying to parse some XMP profile, however it fails at this when there is a lot of XMP-metadata in the file. We're currently working around this issue by stripping Adobe's metadata before feeding the file to ImageMagick. Only stripping Adobe's metadata, which is the biggest chunk of the embedded XMP-metadata in our files, seems not to be enough always so it seems the XMP-limit is rather low.
Over the last year we have added checks in ImageMagick to help prevent security issues (e.g. aborts, uninitialized values, integer overflow). One new check is that the XMP profiles are compliant. The exception you received suggests that your image has a XMP profile that does not validate. If so, ImageMagick won't process it. If it compliant, it could be a bug in ImageMagick. We'll need a day or two to determine if its a bad profile or a bug in ImageMagick. Stand by.
We cannot reproduce the problem. Post a command-line and a link to an image we can use to reproduce the problem. If we do, we'll seek a patch to fix the problem.