ID: 49501 Comment by: spender at grsecurity dot net Reported By: romain dot riviere at gmail dot com Status: Open Bug Type: Scripting Engine problem Operating System: Gentoo Linux 32bit / PaX PHP Version: 5.*, 6 New Comment:
Due to VMA mirroring, the SEGMEXEC option causes accounted vm usage to double. So you weren't experiencing a memory leak -- you were just being accounted for twice as much memory as you thought you were using. The solution would be to double the resource limit or, if your system is NX-capable and PAE is enabled, use PAGEEXEC. -Brad Previous Comments: ------------------------------------------------------------------------ [2009-09-29 17:18:03] romain dot riviere at gmail dot com Just a quick follow-up on this one. I've finally traced it to PaX's SEGMEXEC feature. I do not know yet if every PaX kernel should display that behaviour, or if it's just VServer's GrSec patch, but disabling SEGMEXEC fixed it for me. I guess the bottomline here is : not PHP's fault Cheers ! ------------------------------------------------------------------------ [2009-09-12 13:51:39] romain dot riviere at gmail dot com Unfortunately, same difference (Fatal error: Out of memory (allocated 9175040) (tried to allocate 1048577 bytes) in /home/smokey/test.php on line 15). I need to take some time and experiment a different kernel, with different combinations of VServer/PaX/Grsecurity options, and see if it helps. ------------------------------------------------------------------------ [2009-09-10 06:44:18] romain dot riviere at gmail dot com I was able to reproduce the problem even with the latest sources. I am beginning to suspect PaX/GrSecurity. Are there any catches to be aware of when running PHP in that context ? I know of the --with-pic/TEXTREL issue, but apparently there must be something else to it. ------------------------------------------------------------------------ [2009-09-09 19:43:33] j...@php.net And make sure you really do simply this: 1. Unpack sources 2. ./configure --disable-all --disable-cgi && make 3 run the test script with 'sapi/cli/php -n -d memory_limit=128M yourscript.php ------------------------------------------------------------------------ [2009-09-09 19:42:25] j...@php.net Please try using this snapshot: http://snaps.php.net/php5.2-latest.tar.gz For Windows: http://windows.php.net/snapshots/ I can not reproduce this at all on several different servers running latest svn checkout. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/49501 -- Edit this bug report at http://bugs.php.net/?id=49501&edit=1
