[wp-trac] [WordPress Trac] #52143: memory_limit not always adhered

[WordPress Trac]

#52143: memory_limit not always adhered
-------------------------------+------------------------------
 Reporter:  danielbareman      |       Owner:  (none)
     Type:  enhancement        |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  General            |     Version:  5.6
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:  performance
-------------------------------+------------------------------
Changes (by mikeschroder):

 * keywords:   => reporter-feedback


Comment:

 Hi @danielbareman!

 Thanks for opening the ticket.

 The intent behind the define, so I understand it, is to provide reasonable
 defaults / expectations for PHP memory, and raise that value when
 appropriate.

 Here's the start of the relevant code:
 https://github.com/WordPress/wordpress-
 develop/blob/029dd1bbb929eec4df5f57789ef42c076aab83f0/src/wp-includes
 /default-constants.php#L37

 It looks like when it is not able to be changed by WordPress, the behavior
 is as you suggest:
 https://github.com/WordPress/wordpress-
 develop/blob/029dd1bbb929eec4df5f57789ef42c076aab83f0/src/wp-includes
 /default-constants.php#L43

 It sounds like maybe you're looking for WordPress to keep itself and
 plugins from going over a certain amount of memory, or am I mistaken?
 Could you please explain a bit more the symptoms of the issue you're
 having? Would be interested in understanding the use-case.

 Thanks again!

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