[wp-trac] [WordPress Trac] #32075: Only set WP_MAX_MEMORY_LIMIT by default when its greater than memory_limit

WordPress Trac noreply at wordpress.org
Fri Jul 8 12:56:00 UTC 2016


#32075: Only set WP_MAX_MEMORY_LIMIT by default when its greater than memory_limit
---------------------------------------------+-----------------------
 Reporter:  danielbachhuber                  |       Owner:  ocean90
     Type:  defect (bug)                     |      Status:  accepted
 Priority:  normal                           |   Milestone:  4.6
Component:  Bootstrap/Load                   |     Version:  3.2
 Severity:  normal                           |  Resolution:
 Keywords:  has-patch has-unit-tests commit  |     Focuses:
---------------------------------------------+-----------------------

Comment (by ocean90):

 Replying to [comment:34 ocean90]:
 > In [changeset:"38013"]:
 > {{{
 > #!CommitTicketReference repository="" revision="38013"
 > Bootstrap: Clean up `wp_convert_hr_to_bytes()`.
 >
 > * Don't return a value higher than `PHP_INT_MAX`.
 > * Add unit tests.
 >
 > Props jrf.
 > See #32075.
 > }}}

 Note: I didn't change it to use `substr()` because it was between 5 and 7
 times slower than the current implementation.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/32075#comment:35>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list