ID: 16360 Comment by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: No Feedback Bug Type: Scripting Engine problem Operating System: Linux, Windows, Tru64 PHP Version: 4.0CVS-2002-07-09 New Comment:
After upgrading from PHP 4.0.6 to 4.2.3 (stable) I experience the same problem - using the demonstration script 1 Apache/PHP dies with Segmentation fault (11). Using demonstration script 2 I only get an error indicating that the memory limit (8MB) has been exhausted. Previous Comments: ------------------------------------------------------------------------ [2002-09-23 07:28:10] [EMAIL PROTECTED] No feedback was provided. The bug is being suspended because we assume that you are no longer experiencing the problem. If this is not the case and you are able to provide the information that was requested earlier, please do so and change the status of the bug back to "Open". Thank you. ------------------------------------------------------------------------ [2002-08-28 19:56:18] [EMAIL PROTECTED] Please try using this CVS snapshot: http://snaps.php.net/php4-latest.tar.gz For Windows: http://snaps.php.net/win32/php4-win32-latest.zip The problem no longer seems to happen with the latest CVS on Linux & Windows. ------------------------------------------------------------------------ [2002-07-09 05:42:36] [EMAIL PROTECTED] This happens on Tru64 with current CSV-Snapshot php4-200207090000 > php-test/bin/php theline.php Unaligned access pid=10795 <php> va=0x140062b7c pc=0x1201ab460 ra=0x1201ab454 inst=0xb4010000 FATAL: emalloc(): Unable to allocate 71 bytes ------------------------------------------------------------------------ [2002-04-03 20:48:33] [EMAIL PROTECTED] I'm not sure if this is the same problem, but I get something extremely similar. Install PHP 4.1.x (whether .1 or .2) and suddenly Apache begins growing, and growing, and GROWING in memory use. Eventually a malloc/segfault occurs and Apache either restarts or simply fails outright. Reverting to 4.0.6 resolves the issue, placing 4.1.x back on reintroduces it. No Zend, no nothing other than GZIP and MySQL. Since numerous malloc/segfaults end up leaving Apache unable to restart itself, and PHP 4.1.2 was a security fix and thus HAD to upgrade to it (previously just stuck with 4.0.6 due to this), I have had to configure Apache to auto-restart itself every few hundred hits - this seems to prevent the fault occurring. Mind you PHP still fills up the error log with sh#tloads of parse errors - out of say several hundred executions of a simple 1 line script for example it'll suddenly decide on the next excution to suffer a parse error. Again specific to PHP 4.1.x Sorry if this isn't the same fault? ------------------------------------------------------------------------ [2002-04-02 10:24:07] [EMAIL PROTECTED] why not? ------------------------------------------------------------------------ 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/16360 -- Edit this bug report at http://bugs.php.net/?id=16360&edit=1
