[wp-trac] [WordPress Trac] #14889: Memory Comparison Broken / WordPress Memory Limit

[WordPress Trac]

#14889: Memory Comparison Broken / WordPress Memory Limit
------------------------------+-----------------------------
 Reporter:  hakre             |       Owner:
     Type:  defect (bug)      |      Status:  new
 Priority:  normal            |   Milestone:  Future Release
Component:  General           |     Version:  3.0
 Severity:  normal            |  Resolution:
 Keywords:  has-patch commit  |
------------------------------+-----------------------------

Comment (by hakre):

 Replying to [comment:40 aaroncampbell]:
 > Replying to [comment:39 hakre]:
 > Thanks for digging that up (#3141).  Three years ago in WordPress years
 is basically forever, so we probably just didn't remember WHY it was there
 and thus we were keeping it just to be safe.
 >
 > I'll check and see whether it should be removed or whether we actually
 need a new way to tell if PHP was compiled with --enable-memory-limit.
 Maybe Ryan will remember more about it.

 Okay, then I think this information is helpful then:

 [http://php.net/manual/en/ini.core.php#ini.memory-limit memory_limit -
 Description of core php.ini directives]:
 > '''memory_limit''' ''integer''
 >
 > This sets the maximum amount of memory in bytes that a script is allowed
 to allocate. This helps prevent poorly written scripts for eating up all
 available memory on a server. Note that to have no memory limit, set this
 directive to -1.
 >
 > '''Prior to PHP 5.2.1'''  in order to use this directive it had to be
 enabled at compile time by using --enable-memory-limit in the configure
 line. This compile-time flag was also required to define the functions
 memory_get_usage() and memory_get_peak_usage() prior to 5.2.1. [emphasis
 added][...]

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