[wp-trac] [WordPress Trac] #49329: memory_limit in site health is not really correct, value is taken from wp_raise_memory_limit

[WordPress Trac]

#49329: memory_limit in site health is not really correct, value is taken from
wp_raise_memory_limit
-------------------------------------------------+-------------------------
 Reporter:  espiat                               |       Owner:
                                                 |  SergeyBiryukov
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  5.5
Component:  Site Health                          |     Version:  5.3.2
 Severity:  normal                               |  Resolution:
 Keywords:  needs-testing 2nd-opinion needs-     |     Focuses:
  patch                                          |  administration
-------------------------------------------------+-------------------------

Comment (by JavierCasares):

 I understand the problem, but I think is a terminology one... We are
 showing the "PHP memory limit", so, we show the information PHP is telling
 us... we cannot check the hardware information (at least, easily from a
 simple PHP query)...

 So, if we show "PHP memory limit" and we get the information from the
 ini_get, this should be real. If a plugin modifies the information, is
 also real, because ''is what PHP uses''. If the user, hosting, or plugin
 do a bad configuration (setting more memory that the machine has) is
 something we cannot test (at least, as I said, not easily from the
 WordPress perspective).

 We can check the "PHP initial memory limit" and "PHP memory limit to use"
 (or whatever), as the original ticket said, but I don't think is a good
 idea to stop this because we don't have access to the real memory.

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