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

WordPress Trac wp-trac at lists.automattic.com
Wed Feb 2 22:41:16 UTC 2011


#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 3.2-early  |
---------------------------------+-----------------------------

Comment (by hakre):

 Replying to [comment:13 chrisbliss18]:
 > The ini_get function returns the value as it was set. So if I set in my
 php.ini "7.5G" (which is invalid and treated as 7G by PHP), it still
 returns "7.5G".

 Thanks for the insight.

 >
 > I tested to confirm that 7.5G does indeed translate into 7G in PHP, and
 it does. Since this is the case, I force the value to an int since that is
 how PHP works with it.

 Can you test what happens if you write {{{7.5G 64M}}} into the ini? Into
 what is this translated then?

 >
 > As for the test cases you propose, the first is invalid as it was
 already determined earlier in the conversation that WP_MEMORY_LIMIT will
 be restricted to only supplying a meg format. The second one works as
 expected with the patch I supplied.

 That restriction is a virtual one only. I did it here so to have a de-
 facto specification to go around any issue in the process of assuming for
 this ticket. So to say: "Fixing the issues by not changing any code."
 (a.k.a as "wontfix")

 >
 > I've tested the code supplied and have provided my test code for review.
 Can I please get someone that is willing to try the code to sign off on it
 so we can get this in 3.1? I'm helping at least 3 people a week fix this
 problem.

 Yeah would be great to see something at least in 3.1 but I don't want to
 sound rude to you, FWIK about WordPress core developement, this or
 anything related will make it into 3.1. Not my fault thought. If my
 opinion would count at least a patch that would bring administrators into
 control of memory configuration again would make it into 3.0.5 even.

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


More information about the wp-trac mailing list