[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-patch   |     Focuses:  administration
--------------------------+-----------------------------

Comment (by SergeyBiryukov):

 Replying to [comment:17 zodiac1978]:
 > > I'm on a hoster with 128M PHP memory limit. In Site Health it shows at
 the moment as 256M, because of this bug. Unfortunately you can *set* this
 higher limit without any errors, although the available memory is still
 128M.
 >
 > Although my *real* memory limit is 128M, WordPress will show as the
 second value now *always* as 256M. No matter what the server is having as
 a real limit. This is confusing IMHO.

 Could you see what [https://www.php.net/manual/en/function.posix-
 getrlimit.php posix_getrlimit( 'totalmem' )] returns in that environment?

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