Running PHP Version 7.1.30 under RHEL 7.7.
I’m wanting to bump memory_limit, but wasn’t sure if I had the syntax right (i.e. 256M or 256MB). So to start with I put a bad value “Hugo” in as the memory_limit setting. The trouble with this is the result of phpinfo() (run under httpd) literally has the string “Hugo” in place, i.e.:
So this has me somewhat concerned that PHP doesn’t actually do any sanity checking for the value(s). (If the value provided was bad I would expect it to revert to a default, e.g.)
Can anyone comment on this – in particular, how do you know whether PHP will be enforcing things (if an arbitary string can be provided).
2
Answers
First thing first,
We first need to understand how PHP.ini work in the way of interpretation workflow.
memory_limit is directives for PHP.
when using with PHP function you have to do something like this
ini_set(‘memory_limit’,’256MB’)
. So, this function will temporarily set your value to the interpreter variable. If you see closer then you can get the two columns One is for the Local and One is for global. That shows the capability of the values to the individual respectively.But, When you defined for global you need to set as a suffix with K, M, G respectively. If we exceed this value using apache .htaccess it requires the same for the PHP fpm.
The confusing thing here is that the setting looks like an integer with some special syntax, but is internally defined as a string. The string is then parsed into a separate global variable whenever the value is changed. Crucially, the result of parsing the string to an integer isn’t saved back to the settings table, so when you call
phpinfo()
, you see the original input, not the parsed value.You can see this in the source:
zend_atol
, which handles the special suffixesThe supported syntax is ultimately defined in
zend_atol
, which:g
,G
,m
,M
,k
, orK
A value with no digits at the start will be parsed as zero. When setting the global variable, this will set the memory limit to the minimum allowed, based on the constant
ZEND_MM_CHUNK_SIZE
.You can see the effect by setting the memory limit, then running a loop that quickly allocates a large amount of memory and seeing what comes out in the error message. For instance: