From ecb18ffc05cebcc134c894c1a7f8aa8e76f68cb7 Mon Sep 17 00:00:00 2001 From: Ryan Boren Date: Mon, 3 Dec 2012 19:44:58 +0000 Subject: [PATCH] Increase the PHP memory_limit to WP_MAX_MEMORY_LIMIT in WP_Image_Editor_Imagick. Props DH-Shredder fixes #22699 git-svn-id: https://develop.svn.wordpress.org/trunk@22997 602fd350-edb4-49c9-b593-d223f7449a82 --- wp-includes/class-wp-image-editor-imagick.php | 3 +++ 1 file changed, 3 insertions(+) diff --git a/wp-includes/class-wp-image-editor-imagick.php b/wp-includes/class-wp-image-editor-imagick.php index 03485b5f9a..02dfe03f79 100644 --- a/wp-includes/class-wp-image-editor-imagick.php +++ b/wp-includes/class-wp-image-editor-imagick.php @@ -119,6 +119,9 @@ class WP_Image_Editor_Imagick extends WP_Image_Editor { if ( ! is_file( $this->file ) && ! preg_match( '|^https?://|', $this->file ) ) return new WP_Error( 'error_loading_image', __('File doesn’t exist?'), $this->file ); + // Even though Imagick uses less PHP memory than GD, set higher limit for users that have low PHP.ini limits + @ini_set( 'memory_limit', apply_filters( 'image_memory_limit', WP_MAX_MEMORY_LIMIT ) ); + try { $this->image = new Imagick( $this->file );