#21262 [Opn->Fbk]: crash or fail when outputting large amounts of text quickly
ID: 21262 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -Status: Open +Status: Feedback Bug Type: Performance problem Operating System: WinXP PHP Version: 4.3.0 New Comment: Why can't you install that SP1?? Others reported it fixes this issue, so.. Previous Comments: [2003-02-03 22:45:20] [EMAIL PROTECTED] I can't install SP1 here, but I wouldn't be surprised. This does counter iliaa's "by design" theory. [2003-02-03 11:32:57] [EMAIL PROTECTED] [Update] Just to confirm further after many more hours of use that installing Micrsoft's WinXP Service Pack-1 has fixed this bug for me. [2003-01-29 00:06:12] [EMAIL PROTECTED] Does the solution provided by [EMAIL PROTECTED] fix the problem for you..? [2003-01-28 13:27:42] [EMAIL PROTECTED] I have managed to solve my problem with outputting large amounts of data under WinXP Home Edition, PHP 4.3.0 and Apache 2.0.44. I experienced this problem consistently with a php page that I had written. I installed Windows XP Service Pack-1 from Microsoft and it fixed the problem straight away. To convince myself further I tried the php script listed at the beginning of this bug thread which I previously experienced the same problem. This also works with the service pack installed. It looks like a bug on Microsoft's side of the fence. Try installing the service pack for yourself and email this thread with your results as it worked for me. Good luck. Regards [2003-01-22 20:13:36] [EMAIL PROTECTED] My attitude is a result of iliaa's disrespect for MY time and work on this. I have nothing but respect for people that volunteer to improve PHP. Like I am doing myself by trying to point out bugs. I don't get paid to try OVER AND OVER to get people to recognize problems, and it is less fun than just fixing them myself would be, I assure you. But I have other projects I am committed to. The most I can do is keep pushing through the bureaucratic atmosphere created by people more interesting in closing bugs than fixing them. As I mentioned before, it's very much like trying to get bugs fixed at Microsoft. I don't know why, but this open source project has managed to duplicate the beauracracy aspect of large corporations very well. Perhaps its a lack of accountability from the lack of personal code ownership. Anyway, I submit to you that in NO CASE should PHP exit in an error condition without showing an error message. If this is INTENDED behavior then let me see the words "memory exceeded, quitting". Until I see them, this is a bug. In fact, I very much doubt that this is intended behavior. When the buffer is full, PHP waits for it to be transmitted then continues. It does not simply crash. To state that crashing is "not a bug" shows a fundamental misunderstanding of programming, and indeed of the difference between all that is good and evil. 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
#21262 [Opn->Fbk]: crash or fail when outputting large amounts of text quickly
ID: 21262 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -Status: Open +Status: Feedback Bug Type: Performance problem Operating System: WinXP PHP Version: 4.3.0 New Comment: Does the solution provided by [EMAIL PROTECTED] fix the problem for you..? Previous Comments: [2003-01-28 13:27:42] [EMAIL PROTECTED] I have managed to solve my problem with outputting large amounts of data under WinXP Home Edition, PHP 4.3.0 and Apache 2.0.44. I experienced this problem consistently with a php page that I had written. I installed Windows XP Service Pack-1 from Microsoft and it fixed the problem straight away. To convince myself further I tried the php script listed at the beginning of this bug thread which I previously experienced the same problem. This also works with the service pack installed. It looks like a bug on Microsoft's side of the fence. Try installing the service pack for yourself and email this thread with your results as it worked for me. Good luck. Regards [2003-01-22 20:13:36] [EMAIL PROTECTED] My attitude is a result of iliaa's disrespect for MY time and work on this. I have nothing but respect for people that volunteer to improve PHP. Like I am doing myself by trying to point out bugs. I don't get paid to try OVER AND OVER to get people to recognize problems, and it is less fun than just fixing them myself would be, I assure you. But I have other projects I am committed to. The most I can do is keep pushing through the bureaucratic atmosphere created by people more interesting in closing bugs than fixing them. As I mentioned before, it's very much like trying to get bugs fixed at Microsoft. I don't know why, but this open source project has managed to duplicate the beauracracy aspect of large corporations very well. Perhaps its a lack of accountability from the lack of personal code ownership. Anyway, I submit to you that in NO CASE should PHP exit in an error condition without showing an error message. If this is INTENDED behavior then let me see the words "memory exceeded, quitting". Until I see them, this is a bug. In fact, I very much doubt that this is intended behavior. When the buffer is full, PHP waits for it to be transmitted then continues. It does not simply crash. To state that crashing is "not a bug" shows a fundamental misunderstanding of programming, and indeed of the difference between all that is good and evil. [2003-01-22 19:55:14] [EMAIL PROTECTED] You really need to correct your attitude first. We're all volunteers here and don't get paid for this shit.. [2003-01-22 19:49:33] [EMAIL PROTECTED] This is not always reproducible, this is as good as we can come up with. It appears to only reproduce for people unwilling to do anything about it. [2003-01-22 19:47:57] [EMAIL PROTECTED] Please provide a SHORT but complete example script that can be used to reproduce this. (the one you provided doesn't cause any crashes) 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
#21262 [Opn->Fbk]: crash or fail when outputting large amounts of text quickly
ID: 21262 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -Status: Open +Status: Feedback Bug Type: Performance problem Operating System: WinXP PHP Version: 4.3.0 New Comment: Please provide a SHORT but complete example script that can be used to reproduce this. (the one you provided doesn't cause any crashes) Previous Comments: [2003-01-22 19:41:51] [EMAIL PROTECTED] 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? [2003-01-22 17:12:39] [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'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] [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?) 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
#21262 [Opn->Fbk]: crash or fail when outputting large amounts of text quickly
ID: 21262
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
-Status: Open
+Status: Feedback
Bug Type: Reproducible crash
Operating System: WinXP
PHP Version: 4.3.0
New Comment:
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?)
Previous Comments:
[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.
[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<1 ; $Loop++)
{
echo "blah $Loop ";
}
I am also using the SAPI version of PHP in Apache under Windows XP.
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
