[wp-trac] Re: [WordPress Trac] #3141: explicit memory check before starting install

[WordPress Trac]

#3141: explicit memory check before starting install
----------------------------+-----------------------------------------------
 Reporter:  looksaus        |        Owner:  anonymous
     Type:  defect          |       Status:  new      
 Priority:  normal          |    Milestone:  2.4      
Component:  Administration  |      Version:  2.1      
 Severity:  normal          |   Resolution:           
 Keywords:                  |  
----------------------------+-----------------------------------------------
Comment (by darkdragon):

 The memory limit is set by PHP and not by !WordPress. !WordPress will
 happily consume all the available memory.

 However, the problem is that, a lot of PHP 4 hosts and installations are
 stuck at 8 MBs which is just not enough for all that the installation does
 and I believe even for a large blog would crash.

 I often thought that !WordPress should first try to attempt to increase
 the memory dependent on a few factors.

  * ini_set() would have to be enabled, some hosts disable this.
  * Increasing the memory might fail given some other PHP or server
 configuration.

 I've seen other PHP applications attempt this before failing. WordPress
 would need a new function in {{{functions.php}}} that first attempts to
 increase the memory limit before failing.

 This could make the process more difficult since you would have to first
 check how much memory is consumed during loops and sections which cause
 the most memory overhead. However, the workaround would be to just have a
 DEFINE or option that allows the user to increase the memory limit to that
 in {{{wp-settings.php}}} to a default of 32MB. It would be far simple
 solution.

 My memory limit is set to >128MB however, so I have no problems.

-- 
Ticket URL: <http://trac.wordpress.org/ticket/3141#comment:6>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software