#10299 [Ana->Bgs]: CPU and Memory Spike

ID: 10299 Updated by: kalowsky@php.net Reported By: goten@mylaptop.com -Status: Analyzed +Status: Bogus Bug Type: Performance problem Operating System: FreeBSD 4.2 Stable PHP Version: 4.0.4pl1 New Comment: Thank you for taking the time to report a problem with PHP. Unfortunately you are not using a current version of PHP -- the problem might already be fixed. Please download a new PHP version from http://www.php.net/downloads.php If you are able to reproduce the bug with one of the latest versions of PHP, please change the PHP version on this bug report to the version you tested and change the status back to "Open". Again, thank you for your continued support of PHP. Previous Comments: ------------------------------------------------------------------------ [2001-05-20 14:39:37] jmoore@php.net We cant reproduce this so not really critical, reutnring to analysed. - James ------------------------------------------------------------------------ [2001-05-17 09:05:32] zeev@php.net I'm unable to reproduce a fd leak using require_once() or include_once(). Do you have any script that reproduces this problem? We can't really replicate your problem in general, but if somehow there's a resource leak in your setup, lots of different weird things could end up happening. ------------------------------------------------------------------------ [2001-05-09 01:08:11] goten@mylaptop.com What I found out is that using a lot of include_once, require_once + session will trigger the CPU and memory spike. Add database access to the script can speed up the frequency of the spike. And I also found out require_once DO leak memory. pstat -T show that file in use will always increase. Somehow require_once forgot to close the file after use. lsof can give you a clear picture when you use require_once() I changed my code using cookie and require() statement now. And I delete all sess_files in /tmp seems to correct the problem. This is the only change I made to eliminate the problem. I can't reproduce the error now because the code that have problems have been changed and I don't have the backup. But the combination of A lot of include_once, require_once, and session will trigger the spike, I am pretty sure because after I changed all that, the problem disappear. Old session file in /tmp also contribute to the problem as well. BTW, the last time I checked, CVS version 4.06 in late April still have the problem. ------------------------------------------------------------------------ [2001-05-08 19:26:01] zeev@php.net Is this fairly reproducible? If it is, any chance you could build Apache with debug information (--enable-debug in configure), attach to an offending process (gdb /path/to/httpd <PID>), and run a backtrace ('bt')? ------------------------------------------------------------------------ [2001-05-07 12:44:51] derick@php.net marking critical for php 4.0.6 ------------------------------------------------------------------------ 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/10299 -- Edit this bug report at http://bugs.php.net/?id=10299&edit=1