Yep. But at least this particular bug can and should be fixed. I'm pretty much sure that Imagick has some shutdown handler that frees allocated memory, and it works when script is killed after newImage created a huge image, for example. Memory is only leaked when script is killed while thumbnailImage is processing image, so it probably allocates memory using pure malloc, so Imagick's memory manager and/or handler doesn't know anything about it.
In other words, I am sure it is a bug in Imagick, not in php itself.
Yep. But at least this particular bug can and should be fixed. I'm pretty much sure that Imagick has some shutdown handler that frees allocated memory, and it works when script is killed after newImage created a huge image, for example. Memory is only leaked when script is killed while thumbnailImage is processing image, so it probably allocates memory using pure malloc, so Imagick's memory manager and/or handler doesn't know anything about it.
In other words, I am sure it is a bug in Imagick, not in php itself.