#22699 closed defect (bug) (fixed)
Imagick: PHP memory_limit not increased to WP_MAX_MEMORY_LIMIT before load
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | 3.5 | Priority: | normal |
Severity: | normal | Version: | 3.5 |
Component: | Media | Keywords: | has-patch commit |
Focuses: | Cc: |
Description
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
Attachments (1)
Change History (5)
#1
follow-up:
↓ 2
@
12 years ago
- Keywords commit added
- Milestone changed from Awaiting Review to 3.5
#2
in reply to:
↑ 1
@
12 years ago
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.
Rotating a huge image is probably still a major drain.