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 think this is not a bug, but simply an issue of running out of memory, because the data in the buffer simply gets too big. flush() dumps the data inside the buffer to screen and clears the buffer, which is why it wouldn't crash when flush() is used. Previous Comments: ------------------------------------------------------------------------ [2002-12-29 12:01:41] [EMAIL PROTECTED] Setting implicit_flush to ON does not fix it - so maybe adding flush() only helps because it slows it down..? Also, messing with output_buffering has no effect. This problem has been present ever since I started using PHP. Maybe a memory overflow? Can anyone else repro? (note this only happens with the sapi/mod version) ------------------------------------------------------------------------ [2002-12-29 00:05:14] [EMAIL PROTECTED] On the SAPI version of php in Apache under WinXP: for($Loop=0 ; $Loop<100000 ; $Loop++) { echo "blah $Loop "; } (usually) causes IE to abort loading and reload the page many times; eventually it just shows the standard "The page cannot be displayed", "Cannot find server or DNS Error". Netscape simply aborts in the middle, usually around 50,000. But, sometimes it works fine. If you add a flush() in the loop, the problem goes away. Nothing shows up in the PHP or server error logs, so I assume its a crash. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=21262&edit=1
