Legacy ImageMagick Discussions Archive

Thanks to snibgo's comment, I was able to solve the problem. The solution is indeed to adjust the height and width limits in policy.xml. I think there are actually two underlying problems here: 1. The "-limit width" and "-limit height" command line arguments are ignored. Apparently, these limits can ...

Sure, here is the image in question: http://6jpuwudl6o60u5j2nvzjnd1aq9q.s3-w ... om/pic.jpg

I am using Debian stretrch, kernel 4.8.0-2-amd64.

Thanks for your response. Are these values that I should be able to adjust on the command line? If so, there doesn't seem to be any effect: $ identify -limit memory 4GB -limit map 4GB -limit disk 20GB -limit area 500MP -limit height 50KP -limit width 50KP pic.jpg identify-im6.q16: memory allocation ...

Sorry, I wasn't sure where to post. To answer your questions: $ identify -list resource Resource limits: Width: 16KP Height: 16KP Area: 128MP Memory: 256MiB Map: 512MiB Disk: 1GiB File: 768 Thread: 4 Throttle: 0 Time: unlimited $ free -h total used free shared buff/cache available Mem: 23G 4.3G 1.3G ...

ImageMagick is not able to handle larges images. As you can see in the following code, I am running identify on a JPG of size 624x28281. I've tried to use the -limit parameter to to lift any memory-related restrictions, but there was no change. This seems to be a regression; this was definitely ...