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

[WordPress Trac]

#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 rasobar):

 The WP_MAX_MEMORY_LIMIT variable should become a setting variable.
 Currently it is not listed in wp-config.php nor can an admin set it.
 It defaults to 256M in wp-includes/default-constants.php and is
 overwritten with each WP update.

 Background: At our hosting infrastructure, Suhosin is notifying, when a
 customer's web space allocates more than 256M, which is triggering a
 fail2ban and the admin is finally blocked. We do not want to change the
 rather high 256M limit for any php apps, rather we would like to set
 WP_MAX_MEMORY_LIMIT to 128M , but only once and not after each update.

 Tt may not be exactly the scope with this issue, but should be thought
 together with a memory raise request parameter.

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