Apparently this was a known bug in ImageMagick 6.9.9-15 (and 6.9.9-17)
(https://github.com/ImageMagick/ImageMagick/issues/825). It has been
fixed in version 6.9.9-18.



Reply via email to