ID: 21262 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -Status: Open +Status: Bogus Bug Type: Reproducible crash Operating System: WinXP PHP Version: 4.3.0 New Comment:
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). Previous Comments: ------------------------------------------------------------------------ [2003-01-16 10:20:56] [EMAIL PROTECTED] 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] [EMAIL PROTECTED] 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] [EMAIL PROTECTED] 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] [EMAIL PROTECTED] 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 ------------------------------------------------------------------------ [2003-01-10 23:42:44] [EMAIL PROTECTED] Ridiculous.. how on earth can they look at this: PHP Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 10240 bytes) And say its a bug in IE? I agree with the first assesment - this is a likely a CRITICAL bug. I have seen pages fail for no reason on linux too, who knows if this problem could be responsible. This needs to be looked at by someone at the top. ------------------------------------------------------------------------ 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
