PHP 4.0 Bug #2866 Updated: Apache dumps core and dies, segfault at mod_php4.c:168
| From: | Bug Database | Date: | Thu, 02 Dec 1999 17:31:42 +0000 |
| Subject: | PHP 4.0 Bug #2866 Updated: Apache dumps core and dies, segfault at mod_php4.c:168 | ||
| Groups: | php.dev | ||
| Request: | Send a blank email to php-dev+get-13383@lists.php.net to get a copy of this message | ||
ID: 2866
User Update by: johan@ekenberg.nu
Status: Open
Bug Type: Other
Description: Apache dumps core and dies, segfault at mod_php4.c:168
1. This appears to be (at least partly) duplicating bugs no: 2669, 2848, 2858, 2693 et al., which
all report that max_execution_time (in php.ini) is not honored. I experience the same problem. For
every segfault there is a log-line reporting:
"PHP Fatal error: Maximum execution time of 20 seconds exceeded in [no active file] on line
0"
An infinite loop in a PHP-process will:
a) keep on running without respect to max_execution_time,
b) keep on running even after a browser abort.
2. I don't know whether these are in fact two separate bugs (max_execution_time &
segfaulting), or if they are two outcomes af the same problem.
3. Compiling/running without SSL doesn't seem to make any difference, both segfaults and
max_execution_time violation persist.
Full Bug description available at: http://bugs.php.net/version4/?id=2866