ID: 21262 User updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Open Bug Type: Reproducible crash Operating System: WinXP PHP Version: 4.3.0 New Comment:
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. Previous Comments: ------------------------------------------------------------------------ [2003-01-10 20:58:22] [EMAIL PROTECTED] I had the exact same problem. I submitted a bug report. Bug smashers seemed to go off on some random tangent. Then decided all of a sudden that it was an IE problem (even though in my original report I clearly stated that there was a problem with Mozilla/Netscape output as well). My original bug report here: http://bugs.php.net/bug.php?id=14474 ------------------------------------------------------------------------ [2002-12-30 15:45:50] [EMAIL PROTECTED] Well that's strange, can anyone else repro this? You may need to refresh a few times for it to happen. I have been using PHP from the command line for the last year because of this issue. ------------------------------------------------------------------------ [2002-12-30 10:05:43] [EMAIL PROTECTED] This does not seem to be a problem. I can not reproduce this crash with the following code. for($Loop=0 ; $Loop<100000000 ; $Loop++) { echo "blah $Loop "; } I am also using the SAPI version of PHP in Apache under Windows XP. ------------------------------------------------------------------------ [2002-12-29 15:26:55] [EMAIL PROTECTED] Then maybe this should be a doc change: "If you don't call flush() once in a while, PHP will hang. This is not a bug. Hanging is intentional." This is a BUG. If it causes PHP to HANG before outputting the page, then it is a BUG! FLUSH IS NOT SUPPOSED TO BE MANDATORY. This also happens when outputting pages under 20K, but this example is the best way to repro. And as I stated, implicit flushing does not fix the problem either. Any delay in the loop fixes it. Every time I submit something here, somebody spends 15 seconds on it and marks it as bogus. When it is NOT. I WENT TO THE TIME OF SUBMITTING THIS FOR A REASON, AND I AM NOT A JACKASS. I HAVE BEEN PROGRAMMING FOR 15 YEARS. If you treat every bug report on here like an idiot wrote it, only idiots are going to stick around to report "bugs" for you. Spend a little more than 15 seconds on it. I gave exact details and the simplest repro on earth, not to mention the results of possible contributing factors. What else could you possibly want. Why is it so hard to get problems even acknowledged here? Maybe I should just mark them as bogus in the beginning to save a little time. This is as bad as reporting bugs to Microsoft. ------------------------------------------------------------------------ [2002-12-29 14:08:46] [EMAIL PROTECTED] 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. ------------------------------------------------------------------------ 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
