ID:               31335
 Updated by:       [EMAIL PROTECTED]
 Reported By:      wzaccone at telcordia dot com
-Status:           Open
+Status:           Bogus
-Bug Type:         Unknown/Other Function
+Bug Type:         Scripting Engine problem
 Operating System: Solaris 9
 PHP Version:      4.3.8
 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.

PHP 4.3.10 was already released, but the latest snapshot does include
more fixes.



Previous Comments:
------------------------------------------------------------------------

[2004-12-29 18:19:58] wzaccone at telcordia dot com

tony,I will install the latest snapshot today and let you know. however
because this error occurs randomly, it may not occur for a few days. I
would like to know if you suspect there may be a problem fixed in php
itself?? 
Warren

------------------------------------------------------------------------

[2004-12-29 18:14:52] [EMAIL PROTECTED]

Please try using this CVS snapshot:

  http://snaps.php.net/php4-STABLE-latest.tar.gz
 
For Windows:
 
  http://snaps.php.net/win32/php4-win32-STABLE-latest.zip



------------------------------------------------------------------------

[2004-12-29 17:32:24] wzaccone at telcordia dot com

Description:
------------
recently our users have been seeing the following error occur
frequently but seemingly randomly when using our web application:

fatal error: Maximum execution time of 130 seconds exceeded in xyz.php
line 132

the php file and line number are different each time the error occurs. 
the error does not occur often, every few days or so. 

in our scripts we use the function:  set_time_limit(130);

I have spent much time researching our code, and now I would like to
know if there is any new bug, or session related leak reported in php
4.3.8 which may be causing this problem. Each script we use always ends
normally.  we are using php 4.3.8 on Solaris 9 with Apache 1.3.31.   the
only change we made to php.ini file is we use register_globals on. we
are using session_ids and session variables.  and we do wrap our output
generating code between ob_start();  and ob_end_flush();
thanks.
Warren



------------------------------------------------------------------------


-- 
Edit this bug report at http://bugs.php.net/?id=31335&edit=1

Reply via email to