So from what I understand by reading this bugreport is that there is a workaround by removing the memory rule in /etc/ImageMagick-6/policy.xml - but this file might be overwritten by an security upgrade, right?