ID: 35278 Updated by: [EMAIL PROTECTED] Reported By: maddog2k at maddog2k dot net Status: Open Bug Type: Output Control Operating System: Linux -PHP Version: 4CVS-2005-11-18 (snap) +PHP Version: 5CVS, 4CVS (2005-11-18) (snap) New Comment:
Do us a favor and test with the latest PHP 5 snapshots from now on so we don't have to ask for that separately. Previous Comments: ------------------------------------------------------------------------ [2005-11-18 16:55:42] maddog2k at maddog2k dot net Unfortunately, no change... (php5-200511181330 -> 5.1.0RC7-dev) ------------------------------------------------------------------------ [2005-11-18 16:33:57] [EMAIL PROTECTED] Please try using this CVS snapshot: http://snaps.php.net/php5-latest.tar.gz For Windows: http://snaps.php.net/win32/php5-win32-latest.zip ------------------------------------------------------------------------ [2005-11-18 16:33:34] maddog2k at maddog2k dot net Description: ------------ Bug #35264 was fixed, but this introduced a new Apache child segmentation fault, under some conditions. With PHP 4.4.0 and below, the following would work correctly with Apache 2.0.54/.55 : AddOutputFilter INCLUDES .php AddType application/x-httpd-php .php Then having a .php that contains multiple (eg. 2) <!--#include virtual="/page.html" --> and for example about 24 thumbnails (of 4.0k each), you read a segfault of an Apache child process in the error_log and the page loading finishes and showing cut-off content. Like I said, the segfault happens since the fix for bug #35264, before it just didn't segfault but stopped loading. When changing output_buffer to 0 or Off, no difference. Only when I set output_buffer => 16384 in php.ini, the page loads completely. Strange thing here is that output buffering isn't used in the page at all, or SSI by default must use buffering... Seems to me that something has changed regarding buffering between 4.4.0 <-> higher versions. Like the memory get's full or so, cause when I delete a few lines of html-code in the page (random), it does load. Noe that this does like an Apache bug or so, but hence it only happens since PHP 4.4.1 Reproduce code: --------------- Hopefully, the description rings a bell at you guys :) But possible if really needed. Expected result: ---------------- Page loads completely (100%) Actual result: -------------- Page loads not completely ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=35278&edit=1
