Imagick: PHP memory_limit not increased to WP_MAX_MEMORY_LIMIT before load

[DH-Shredder]

Currently, the PHP memory_limit is not automatically increased to WP_MAX_MEMORY_LIMIT in Imagick, as it is in GD.

This was initially done because Imagick uses significantly less RAM.
From a basic test, an initial upload does clock at a lot less PHP memory used for a general iPhone 4 JPG upload (34mb peak used vs. 78mb peak).

But, some users with with 32mb limits may have issues with Imagick, where they wouldn't have previously with GD.

http://core.trac.wordpress.org/browser/trunk/wp-includes/class-wp-image-editor-gd.php#L89
http://core.trac.wordpress.org/browser/trunk/wp-includes/class-wp-image-editor-imagick.php#L119

Rotating a huge image is probably still a major drain.

Replying to nacin:

Rotating a huge image is probably still a major drain.

Why? all the imagick handeling isn't in PHP but on a separate process. So the memory usage will not be that different.

In 22997:

Increase the PHP memory_limit to WP_MAX_MEMORY_LIMIT in WP_Image_Editor_Imagick.

Props DH-Shredder
fixes #22699

It does look like even with rotation we're still talking about < 40mb, but generally > 32.

This is something we probably don't need, due to Imagick doing processing in a module, but doesn't hurt, and is indeed a differing behaviour to what GD is doing.