#21262 [Bgs->Opn]: crash or fail when outputting large amounts of text quickly

ID: 21262 User updated by: spagmoid@yahoo.com Reported By: spagmoid@yahoo.com -Status: Bogus +Status: Open -Bug Type: Reproducible crash +Bug Type: Performance problem Operating System: WinXP PHP Version: 4.3.0 New Comment: You are wrong. If it was a memory error, PHP should display the standard out of memory message. AS I EXPLAINED, this also happens with very SMALL amounts of data. The use of large blocks of data is just an easy way to REPRO. Surely there must be more people working on PHP than you? Previous Comments: ------------------------------------------------------------------------ [2003-01-22 17:12:39] iliaa@php.net Thank you for taking the time to write to us, but this is not a bug. Please double-check the documentation available at http://www.php.net/manual/ and the instructions on how to report a bug at http://bugs.php.net/how-to-report.php I've explained before and I will attempt to explain once again. When output buffering is turned on the system does not output the text right away but rather fills up a memory buffer that is displayed in one large block. If the text you are trying to output exceeds the avaliable system memory then the error you are seeing will occur. This cannot be helped, the solution is to either disable output buffering or not use things like gz_handler, which cause ALL of the output to be buffered in memory rather then output the data in chunks (default chunk size 4096 bytes). ------------------------------------------------------------------------ [2003-01-16 10:20:56] spagmoid@yahoo.com This bug has been present for over a year, maybe since the beginning of PHP. We're still getting people passing the buck.. ------------------------------------------------------------------------ [2003-01-15 16:44:33] gmeakin@btinternet.com I am using Apache version 2.0.43 with the sapi php module. I downloaded the latest stable snapshot of php (4.3.1) but it still reproduced the same orignial problem discussed. Regards ------------------------------------------------------------------------ [2003-01-14 19:25:17] sniper@php.net Please try using this CVS snapshot: http://snaps.php.net/php4-STABLE-latest.tar.gz For Windows: http://snaps.php.net/win32/php4-win32-STABLE-latest.zip (and what apache version is it?) ------------------------------------------------------------------------ [2003-01-14 13:34:57] gmeakin@btinternet.com I can confirm this bug including the for loop provided earlier in this bug thread. I am using php 4.3.0 with Apache 2.0.43 with Windows XP Home Edition. I found this bug report after noticing the same effect with a large piece of php that I have been writing. I have found that turning off error reporting in php.ini helps but does not solve the problem totally. I found that using the flush() function helped but was not a reliable solution. This seems a blatant problem which is making debugging and development almost impossible and very frustrating. Is there any update on confirming the bug? Regards ------------------------------------------------------------------------ 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/21262 -- Edit this bug report at http://bugs.php.net/?id=21262&edit=1