[wp-trac] [WordPress Trac] #17083: Users experiencing fatal memory errors in various activities

[WordPress Trac]

#17083: Users experiencing fatal memory errors in various activities
-------------------------------+------------------------------
 Reporter:  bennebw            |       Owner:
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  General            |     Version:  3.1
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |
-------------------------------+------------------------------
Changes (by dd32):

 * keywords:   => reporter-feedback


Comment:

 The WordPress Admin sets the memory limit to 256M if it can for expensive
 operations (Upgrades and Image editing).

 The rest of WordPress runs on 32M for single-site and 64M for multisite
 like you've noticed.

 [http://core.trac.wordpress.org/browser/trunk//wp-includes/default-
 constants.php#L38 A few lines down from that], you'll find it's only set
 to 32/64M if thats greater than the current memory limit (Note: If you
 express the php memory limit in Gigabytes, you'll run into #14889)

 I'd be questioning what the memory limit is -really- set to.. try
 phpinfo(); in it's own file and check what the memory_limit claimed there
 is? or add `echo init_get('memory_limit');` to your wp-config.php file
 temporarily to check what the actual PHP value is before WordPress loads.

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