[wp-trac] [WordPress Trac] #13307: 3.0 package size will cause memory limit problems

WordPress Trac wp-trac at lists.automattic.com
Fri May 21 21:17:42 UTC 2010

#13307: 3.0 package size will cause memory limit problems
 Reporter:  nacin            |        Owner:  nacin   
     Type:  defect (bug)     |       Status:  reopened
 Priority:  highest omg bbq  |    Milestone:  3.0     
Component:  General          |      Version:  3.0     
 Severity:  blocker          |   Resolution:          
 Keywords:                   |  
Changes (by Denis-de-Bernardy):

  * status:  closed => reopened
  * resolution:  fixed =>


 Replying to [comment:45 ryan]:
 > The workaround is to do a manual upgrade. I think we've done enough

 As much as you've probably merely fixed enough of the symptoms for now,
 you've left the causes untouched. I would know, in that I've been
 distributing a WP zip that is 3MB+ since WP 2.5. The causes are the huge
 number of files, WPFS, and the unzip() function. Those ought to be
 optimized. Heavily.

 At 2.9M, you're at the point where problems start to appear on servers
 with the suhosin patch and multitudes of apache/php modules. You might not
 get many in 3.0, but I can guarantee you that you'll get quite a few as
 the zip's size increases.

 I'm re-opening because, for users who experience the issue, a manual
 upgrade is the last thing they think of. We should add a notice on the
 upgrade screen. Along the lines of:

 "The upgrader doesn't work on all servers. If the upgrade fails on your
 server, don't panic! Upgrade WP manually by following these instructions
 (with a link to a codex article), and things will be fine." (Note: the
 instructions should tell users to delete the .maintenance file.)

Ticket URL: <http://core.trac.wordpress.org/ticket/13307#comment:47>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software

More information about the wp-trac mailing list