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

WordPress Trac noreply at wordpress.org
Sat May 16 08:24:21 UTC 2020


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

 I have two hoster with 128M real memory limit.

 The first is showing `524288000` and the second one is showing `unlimited`
 for soft and hard totalmem. So both values are incorrect in the matter of
 the current available memory.

 With `ini_get( 'memory_limit' );` I get the correct value of 128M in both
 cases (if not in WP environment).

 The problem is: I can use `ini_set( 'memory_limit', '256M' );` and then
 `ini_get( 'memory_limit' );` shows 256M (instead of the correct 128M).

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


More information about the wp-trac mailing list