You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The cli_check.php uses the built in PHP functions to get the details so if it reports 400M that is what is being returned by ini_get() within the function in install/functions.php.
I don’t believe we have a hard coded value as default though if we did, that would mean that we aren’t getting the memory limit back. Since I’ve tested that functionality recently, I know it picked up my memory limit.
This seems to have been introduced by #2712 (Memory limit should be unlimited) as the variable $original_memory_limit was removed which is used by the utility if present. The cli_check.php routine did set that before setting the memory to 500M before but as part of the conversion it was accidentally removed.
I don't think it's a big impact on upgrade since most systems will already have the right value, but new installs may not.
Describe the bug
cli_check.php return incorrect memory_limit
Maybe, cli_check.php output is impacted by some ini_set usage
To Reproduce
The text was updated successfully, but these errors were encountered: