ID: 50531
User updated by: net_php at mojocafe dot jp
Reported By: net_php at mojocafe dot jp
-Status: Feedback
+Status: Open
Bug Type: *General Issues
Operating System: OS 10.6.2
PHP Version: 5.3.1
New Comment:
I think it is not that latter script because other basic scripts don't
time out.
Previous Comments:
------------------------------------------------------------------------
[2009-12-21 12:14:50] j...@php.net
Maybe this is same as bug #49868 (max_execution_time affected by
max_input_time). So try the latest snapshot first.
------------------------------------------------------------------------
[2009-12-21 12:11:33] j...@php.net
The obvious next question is: Where's the reproducing script..?
------------------------------------------------------------------------
[2009-12-21 11:41:04] net_php at mojocafe dot jp
Yes. This is a CLI script.
------------------------------------------------------------------------
[2009-12-21 11:39:48] net_php at mojocafe dot jp
Sorry, yes, the original submission uses the word 'crash' but that was
mistaken: 'terminates with fatal error' is what I meant.
11:36:44 $ php -i | grep _time
allow_call_time_pass_reference => On => On
max_execution_time => 0 => 0
max_input_time => -1 => -1
mysql.connect_timeout => 180 => 180
default_socket_timeout => 60 => 60
------------------------------------------------------------------------
[2009-12-21 11:31:52] j...@php.net
First of all, this is NOT any crash. Does it happen on command line?
What does this output:
# php -i | grep _time
------------------------------------------------------------------------
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/50531
--
Edit this bug report at http://bugs.php.net/?id=50531&edit=1
