ID: 21262
Comment by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Open
Bug Type: Performance problem
Operating System: WinXP
PHP Version: 4.3.0
New Comment:
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
Previous Comments:
------------------------------------------------------------------------
[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)
------------------------------------------------------------------------
[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?
------------------------------------------------------------------------
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
