-
-
Notifications
You must be signed in to change notification settings - Fork 133
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
identifyFormat(%[profile:icc]) aborts execution #628
Comments
Ugh, to set your expectations, that looks like a bug in ImageMagick (the underlying library that does the actual work), rather than in Imagick. Please could you send me that image or file that shows that behaviour. As a mitigation attempt, can you do |
Hello, Danack: $im is well populated. As far as I tested, other format strings works flawlessly:
I've found a workaround by iterating getImageProfiles() and using a custom function to parse the result (not so clean):
I think the root cause could be ImageMagick not getting the Image Properties for icc
In fact, after little research, identify CLI also fails:
But Imagick aborts instead raising an exception. Thanks for your help. |
Yeah. As you've got a reproduce case on the command line, I'd recommend opening a bug upstream at https://github.com/ImageMagick/ImageMagick or https://github.com/ImageMagick/ImageMagick6 if you're still on ImageMagick6. I'll have look to see if I can handle the failing case better. Can you either email me or upload an example image that shows this behaviour please? |
After doing some more research, I found the main problem. It has nothing to do with the image. Windows
Linux
After rebuilding ImageMagick with lcms support, the icc properties are working as expected. So, the only thing missing would be throwing an exception when identifyFormat is invoked with a wrong property instead of aborting. One more time, thanks for your help. |
Hello again,
Trying to find the ICC profile name of an image:
the script aborts and the following message is logged:
Thanks in advance.
The text was updated successfully, but these errors were encountered: