ID: 44954 Updated by: [EMAIL PROTECTED] Reported By: abakker at gmx dot net -Status: Open +Status: Feedback Bug Type: Reproducible crash Operating System: Win XP PHP Version: 5.2.6 New Comment:
The problem is that I can't reproduce this. So it's up to you either provide the backtrace or just let this report rot. Previous Comments: ------------------------------------------------------------------------ [2008-07-24 09:10:43] abakker at gmx dot net I tried to create a backtrace for the httpd.exe process, but no dmp file is generated. Either Apache does not crash (but hangs) or I am doing something wrong. The problem can easily be reproduced (just run the script I provided). I suggest you reproduce the problem yourself which allows you to do whatever analysis or backtracing you need. That would be far more efficient than passing it back to me. ------------------------------------------------------------------------ [2008-07-14 21:13:40] [EMAIL PROTECTED] Thank you for this bug report. To properly diagnose the problem, we need a backtrace to see what is happening behind the scenes. To find out how to generate a backtrace, please read http://bugs.php.net/bugs-generating-backtrace.php for *NIX and http://bugs.php.net/bugs-generating-backtrace-win32.php for Win32 Once you have generated a backtrace, please submit it to this bug report and change the status back to "Open". Thank you for helping us make PHP better. ------------------------------------------------------------------------ [2008-05-18 08:43:37] abakker at gmx dot net I added a sleep(1) and set max_execution_time to 999. After 172 iterations the Apache server hangs (does not respond to page requests anymore). The script continues very slowly at this point, it times out on every file_get_contents request (in the error log you see the error message mentioned at the top of this bug report for every iteration). The total number of threads in Windows Task Manager does not increase when running the script. My system is also not running out of resources, I have 3 Gb memory of which 2.6 Gb is available. When you replace file_get_contents with http_get or curl_exec the problem does not occur. Seems to me that this indicates that there is something wrong with file_get_contents. In any case a PHP script should not cause the Apache server to hang/crash (Apache does not respond to page requests for any user anymore) and bring a production system down. ------------------------------------------------------------------------ [2008-05-18 00:20:28] [EMAIL PROTECTED] I really doubt this is any bug in PHP anyway. You propably just run out of Apache threads/childs with that script that doesn't really give Apache any chance. Try adding some 'sleep(1);' line inside the for() loop. ------------------------------------------------------------------------ [2008-05-11 11:15:41] abakker at gmx dot net In the Apache error log it just says the connected party failed to respond (the complete message is in the beginning of this bug report). I tried the backtrace tools, but did not manage to get a backtrace. I looked at the processes. I have two httpd.exe processes when I start Apache. When I reproduce the problem, the two processes remain. I guess technically this means the Apache server does not crash, but hangs and this is the reason why I do not get a backtrace? Anyway, the two httpd.exe processes keep on running, but any web page request fails (internet explorer displays the standard page that it could not access the requested web page). Apache no longer seems to respond to requests. The two httpd.exe processes use no cpu when the problem occurs. A restart of Apache does not give any error message, but does not solve the issue. A stop and start is needed. Not sure whether this tells you something. Anyway, were you able to reproduce the problem yourself? That would be helpful, if so, you could do any backtracing or other diagnosis yourself. I am not familiar with the diagnostic tools, it would be much better if you could do it. ------------------------------------------------------------------------ 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/44954 -- Edit this bug report at http://bugs.php.net/?id=44954&edit=1
