The upstream comment indicates the issue is believed to be in imagemagick itself rather than php-imagick. It would be worth re-testing if this issue exists or not when using current imagemagick.
The upstream comment indicates the issue is believed to be in imagemagick itself rather than php-imagick.
It would be worth re-testing if this issue exists or not when using current imagemagick.