#16360 [Ana->Fbk]: Segmentation fault in Array functions

ID: 16360 Updated by: iliaa@php.net Reported By: nohn@php.net -Status: Analyzed +Status: Feedback Bug Type: Scripting Engine problem Operating System: Linux, Windows, Tru64 PHP Version: 4.0CVS-2002-07-09 New Comment: 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. Previous Comments: ------------------------------------------------------------------------ [2002-07-09 05:42:36] nohn@php.net 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] chris@dvdplaza.com.au 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] wolfram@schlich.org why not? ------------------------------------------------------------------------ [2002-04-01 21:58:51] yohgaki@php.net My personaly preference is "result must be correct always, if not raise error", but it's not the case under PHP, unfortunately. ------------------------------------------------------------------------ [2002-04-01 09:00:25] wolfram@schlich.org Ok, ZendOptimizer disabled, patch works as expected. Any patch like the one Joerg suggested in sight? ------------------------------------------------------------------------ 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