Occasional 1-pixel horizontal band in output
Posted: 2015-05-14T17:41:21-07:00
We're using the version of ImageMagick in CentOS 7, 6.7.8-9, and we're randomly getting a 1-pixel horizontal band (e.g., all black or all white pixels) somewhere in the middle of JPEGs that are being scaled down. Here's a sample command line:
convert -limit map 512mb -limit memory 512mb -limit thread 1 -flatten -scale '1000x1000>' -scale '1000x1000<' -quality 85 -define registry:temporary-path=/opt/lightbox/magick '/opt/lightbox/appfiles/thumbs/thm254sXw/fullIsPm3V.jpg' '/opt/lightbox/appfiles/thumbs/thm254sXw/fullzzVknh.jpg' 2>&1
or
convert -limit map 512mb -limit memory 512mb -limit thread 1 -size 1000x1000 -quality 85 -flatten -scale 1000x1000 '/opt/lightbox/appfiles/thumbs/thm254sXw/fullzzVknh.jpg[1000x1000]' '/opt/lightbox/appfiles/thumbs/thm254sXw/thmFgRpHD.jpg' 2>&1
("flatten" is present because we use the same command with other image types like TIFF and PSD)
This problem is occurring on about 1 out of every 50 images we process this way. We've used many different versions of IM with this app since 2005, and this is the first time I've seen this problem. I searched the release notes for various terms to see if there have been any bugs fixed with this symptom, but I couldn't find anything. We can certainly upgrade to a newer version of IM, but I'd like to know if this is/was a known issue at some point and has been addressed, or whether I'm misusing it, or what.
convert -limit map 512mb -limit memory 512mb -limit thread 1 -flatten -scale '1000x1000>' -scale '1000x1000<' -quality 85 -define registry:temporary-path=/opt/lightbox/magick '/opt/lightbox/appfiles/thumbs/thm254sXw/fullIsPm3V.jpg' '/opt/lightbox/appfiles/thumbs/thm254sXw/fullzzVknh.jpg' 2>&1
or
convert -limit map 512mb -limit memory 512mb -limit thread 1 -size 1000x1000 -quality 85 -flatten -scale 1000x1000 '/opt/lightbox/appfiles/thumbs/thm254sXw/fullzzVknh.jpg[1000x1000]' '/opt/lightbox/appfiles/thumbs/thm254sXw/thmFgRpHD.jpg' 2>&1
("flatten" is present because we use the same command with other image types like TIFF and PSD)
This problem is occurring on about 1 out of every 50 images we process this way. We've used many different versions of IM with this app since 2005, and this is the first time I've seen this problem. I searched the release notes for various terms to see if there have been any bugs fixed with this symptom, but I couldn't find anything. We can certainly upgrade to a newer version of IM, but I'd like to know if this is/was a known issue at some point and has been addressed, or whether I'm misusing it, or what.