#35856 [Opn->Fbk]: Segmentation Fault

ID: 35856 Updated by: sniper@php.net Reported By: jseverson at myers dot com -Status: Open +Status: Feedback Bug Type: Output Control Operating System: Linux -PHP Version: 5.1.1 +PHP Version: 5CVS-2005-12-30 (snap) New Comment: Thank you for this bug report. To properly diagnose the problem, we need a backtrace to see what is happening behind the scenes. To find out how to generate a backtrace, please read http://bugs.php.net/bugs-generating-backtrace.php for *NIX and http://bugs.php.net/bugs-generating-backtrace-win32.php for Win32 Once you have generated a backtrace, please submit it to this bug report and change the status back to "Open". Thank you for helping us make PHP better. Previous Comments: ------------------------------------------------------------------------ [2005-12-31 02:28:58] jseverson at myers dot com Yep, we just tried the latest snapshot from CVS 15 minutes ago and experienced the same seg faults. ------------------------------------------------------------------------ [2005-12-31 02:11:34] sniper@php.net Please try using this CVS snapshot: http://snaps.php.net/php5.1-latest.tar.gz For Windows: http://snaps.php.net/win32/php5.1-win32-latest.zip ------------------------------------------------------------------------ [2005-12-31 02:04:56] jseverson at myers dot com The errors we are experiencing are similar to this bug: http://bugs.php.net/bug.php?id=35278 which was supposedly fixed in 5.1.0. ------------------------------------------------------------------------ [2005-12-31 02:03:26] jseverson at myers dot com Description: ------------ We just upgraded to php 5.1.1 on our development slice and have run into all kinds of buffering seg fault issues that seem to be similar to what was reported in this bug. We tried setting output_buffer to off/on/4096, and none of those settings fixed the problem. However, if we up our output_buffer to about 16000, the problem goes away on most pages, but not all. If we then increase our output_buffer to 5000000 then the problem goes away entirely. We were able to isolate where the browser stopped sending HTML, and it seems to be SOMEWHAT related to our use of ob_* functions in one case. However, there were other cases where html would stop outputting literally in the middle of a <td> tag...so if you viewed source, all you would see is: <t Modules are: ctype,curl,date,dom,exif,gd,iconv,libxml,ming,mysql,oci8,pcre,PDO,pdo_mysql,PDO_OCI,posix,session,SimpleXML,smbauth,soap,SPL,standard,sybase,tokenizer,xml,zlib ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=35856&edit=1