[wp-trac] [WordPress Trac] #17507: Hardcoded memory limit

[WordPress Trac]

#17507: Hardcoded memory limit
------------------------------+------------------------------
 Reporter:  christianbolstad  |       Owner:
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:  Awaiting Review
Component:  Performance       |     Version:  3.2
 Severity:  normal            |  Resolution:
 Keywords:  has-patch         |
------------------------------+------------------------------

Comment (by christianbolstad):

 Replying to [comment:1 kawauso]:
 > `wp_load_image()` has a high memory limit because the GD is a memory hog
 and wouldn't necessarily work within the normal limit.
 >
 > Don't really see what the use case for the filter would be either unless
 PHP fails to set the limit at all if it's beyond the maximum allowed by
 server settings.

 The problem is that each @ini_set() call can (depending on the system
 configuration) override the server settings (if AllowOveride is enabled in
 for example Apache). People like me, that need more 256MB memory in some
 cases, have to edit the core file to get more memory. Not very optimal.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/17507#comment:2>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software