PHP 4.0 Bug #9031 Updated: ob_gzhandler memory leak and Headers already sent message!

ID: 9031 User Update by: aboldt@boldtconsult.com Old-Status: Closed Status: Open Bug Type: Performance problem Description: ob_gzhandler memory leak and Headers already sent message! Tried the php4-200102020545 snapshot and I still get the httpd: PHP Warning: Cannot add header information - headers already sent in Unknown on line 0 error message when enabling output_handler = ob_gzhandler. This probably still causes a memory leak. Found another interesting thing: when trying to see the headers of a ob_gzhandler compressed page with lynx, I get the following lynx error message: Can't access startfile http://localhost/test.php That's using lynx -head -source http://localhost/test.php. Seems lynx sees something which it doesn't like. With ob_gzhandler disabled, I get the normal http headers when invoking that lynx command. Previous Comments: --------------------------------------------------------------------------- [2001-02-01 20:03:32] sniper@php.net This should be fixed in CVS now. Please try the latest CVS snapshot from http://snaps.php.net/ and reopen this bug report if problem still exists when using it. --Jani --------------------------------------------------------------------------- [2001-01-31 09:15:17] aboldt@boldtconsult.com When enabling output_handler = ob_gzhandler in php.ini, my Linux system starts to eat more and more memory in an unusual way, like there was a memory leak, like many people have reported. But what is absolutely weird is that after enabling ob_gzhandler, I start to get this error messages in my log files: Cannot add header information - headers already sent in Unknown on line 0 Which is weird, because one of the features of output buffering is to avoid that kind of problems. What's even more weird is that I don't get any "headers already sent" messages with output_handler = ob_gzhandler disabled! --------------------------------------------------------------------------- Full Bug description available at: http://bugs.php.net/?id=9031