#43147 [Com]: Random "PHP Fatal error: Maximum execution time of 60 seconds exceeded"

ID: 43147 Comment by: kirkshafonsky at hotmail dot com Reported By: marquinhocb at hotmail dot com Status: No Feedback Bug Type: Performance problem Operating System: Windows Server 2003 R2 x64 PHP Version: 5.2.5 New Comment: Did you ever solve the problem? I have the same problem on my webserver Win2k, using PHP5.2.5 and MySQL5 I have been searching for a solution. Previous Comments: ------------------------------------------------------------------------ [2008-05-27 01:00:00] php-bugs at lists dot php dot net No feedback was provided for this bug for over a week, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open". ------------------------------------------------------------------------ [2008-05-19 22:54:12] jani@php.net First you should compile PHP in debug mode and preferrably use the latest release: 5.2.6 too.. ------------------------------------------------------------------------ [2008-04-23 14:24:02] marquinhocb at hotmail dot com I have been able to get a setup without any PHP extensions installed (on a seperate server, with similar setup), and I am still able to reproduce the issue. Using PHP 5.2.5. Maximum execution time of 60 seconds exceeded in C:\sites\tgh\index.php on line 22 At line 22: include 'includes/right.inc.php'; All I need is help tracking down this issue with some advice. I am a C/C++ developer and familiar with the inner workings of PHP and how to compile, just need advice on how to instrument PHP code to track this down. Thanks. ------------------------------------------------------------------------ [2007-11-11 19:04:58] jani@php.net Until you have ruled out any interference by 3rd party extensions, keep this in feedback mode. ------------------------------------------------------------------------ [2007-10-31 13:43:58] marquinhocb at hotmail dot com Problem is, like I said, this is on a production server, I can't get it to happen anywhere else (with the same extensions). And even on the production server it happens rarely. My guess is that this is a bug present in PHP that's extremely difficult to reproduce, and that the conditions of my production server make it easier to reproduce. If I remove the extensions, this will break the site, and so it is not a possibility. Not to mention: if it doesn't make the issue go away, we'll be in the same position. So, in essence I need help tracking this down so I can provide more useful information. ------------------------------------------------------------------------ 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/43147 -- Edit this bug report at http://bugs.php.net/?id=43147&edit=1