[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        |   Keywords:
--------------------------+-----------------------------
 A number of users have been reporting on blogs and in the WP forum that
 they are getting fatal memory errors when upgrading to WP 3.1.1 or
 upgrading plugins, also in some image resizing situations.

 I experienced this on several sites while upgrading to WP 3.1.1.  My host
 has a memory limit of 256MB and the error message I got said it was trying
 to allocate around 30MB.  When I deactivated a couple of plugins,
 everything went fine.

 I did a quick search of WP 3.1 and found the following lines in wp-
 includes/default-constants.php:


 {{{
 // set memory limits
         if ( !defined('WP_MEMORY_LIMIT') ) {
                 if( is_multisite() ) {
                         define('WP_MEMORY_LIMIT', '64M');
                 } else {
                         define('WP_MEMORY_LIMIT', '32M');
                 }
         }
 }}}

 So, it looks like for single blog sites (non-MU), that is setting a
 constant for 32M.  Could this be the root of why folks are blowing memory
 even if they've got 256MB from the host?

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