ID: 9031
User Update by: [EMAIL PROTECTED]
Status: Closed
Bug Type: Output Control
Operating system: Linux 2.2.18
PHP Version: 4.0.4pl1
Description: ob_gzhandler memory leak and Headers already sent message!

Problem has already been solved in php 4.0.5.

Previous Comments:
---------------------------------------------------------------------------

[2001-06-14 14:34:19] [EMAIL PROTECTED]
Can't reproduce on PHP 4.0.6RC3

http://www.php.net/~andi/php-4.0.6RC3.tar.gz


---------------------------------------------------------------------------

[2001-02-20 10:43:39] [EMAIL PROTECTED]
The headers already sent message with ob_gzhandler enabled problem is solved.

However, the lynx -head problem is still there.

---------------------------------------------------------------------------

[2001-02-20 06:40:13] [EMAIL PROTECTED]
both problems are fixed in CVS


---------------------------------------------------------------------------

[2001-02-19 23:02:20] [EMAIL PROTECTED]
similar Bug id #9231


---------------------------------------------------------------------------

[2001-02-06 15:33:49] [EMAIL PROTECTED]
I've just found out what the problem is, and it's kind of weird:
With ob_gzhandler enabled (from php.ini or with ob_start("ob_gzhandler") in the .php) 
each readfile() makes the "Cannot add header information - headers already sent" error 
message appear.
This doesn't happen with output buffering enabled and no ob_gzhandler, it only happens 
with ob_gzhandler enabled.

Also tried to replace readfile with fpassthru(fopen()) but got the same result.

Hope this helps you fix the problem.

If you have any questions feel free to ask, I've been experimenting quite a lot.

---------------------------------------------------------------------------

The remainder of the comments for this report are too long.  To view the rest of the 
comments, please view the bug report online.

Full Bug description available at: http://bugs.php.net/?id=9031


-- 
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to