On Sat, 23 Jan 2016, Eric X wrote:
Package: graphicsmagick
Version: 1.3.20-3+deb8u1
Severity: important
Dear Maintainer,
I have an application that passes jpegs to gm convert to resize to roughly
1600x900/900x1600. Since I don't enforce
any aspect ratio and want to have roughly equivalent sizes, I make use of the @
suffix in the -resize option.
When resizing jpegs around 256KB, it seems to work just fine. But on images
around 1MB (and I assume any larger),
gm convert runs forever, using up all the RAM it can and starving the system.
I see that you are using 1.3.20. The parsing/handling of the '@' area
specification was fixed in GraphicsMagick 1.3.22. Without the fix,
the value is likely taken as the image width and height, resulting in
a huge image.
The current upstream release is 1.3.23, which I should hope becomes
the current Debian offering for supported Debian release branches due
to the many security issues fixed by 1.3.21 - 1.3.23.
To limit the pixels consumed by any image (causing an error if there
is an attempt to create an image larger than the area), add an option
like
-limit Pixels 4MP
or set MAGICK_LIMIT_PIXELS in the environment with an argument like
'4MP'.
Bob
--
Bob Friesenhahn
bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
