[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 Apr 1 11:24:46 UTC 2016
#32075: Only set WP_MAX_MEMORY_LIMIT by default when its greater than memory_limit
------------------------------------+-----------------------------
Reporter: danielbachhuber | Owner:
Type: defect (bug) | Status: new
Priority: normal | Milestone: Future Release
Component: Bootstrap/Load | Version: 3.2
Severity: normal | Resolution:
Keywords: has-patch dev-feedback | Focuses:
------------------------------------+-----------------------------
Comment (by mensmaximus):
I would like to throw an other aspect into the discussion. How usefull can
it be to set WP_MAX_MEMORY_LIMIT to 256M by default if the allocated
memory ( ini_get( 'memory_limit' ) ) is less than 256M? What would happen
if a plugin developer would rely on the constants value and this value
exceeds the memory allocated by the server (and restricted by the hosting
company)? Imho the WP_MAX_MEMORY_LIMIT constant should never report a
larger amount of memory than the maximum allocatable memory.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/32075#comment:17>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list