Re: Bug #13806 Updated: zlib compression is not
| From: | Yasuo Ohgaki | Date: | Sun, 11 Nov 2001 08:47:54 +0000 |
| Subject: | Re: Bug #13806 Updated: zlib compression is not | ||
| References: | 1 2 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-70071@lists.php.net to get a copy of this message | ||
Zeev Suraski wrote:
At 03:44 11/11/2001, yasuo_ohgaki@yahoo.com wrote:I didn't compare output.c... but, I had almost the same behavior with 4.1.0 and 4.2.0 when I tested it. But I didn't have problem with 4.2.0 today.result - 4.1.0RC: 4.1.0RC works fine without zlib compression, but not with zlib output compression. httpd just keeps growing when output exceed buf size. (I killed it when it became 100MB) It cannot display phpinfo(). There are many log entry for memory leak for apache. result - 4.2.0: It seems there is no problem in 4.2.0 now. It works for both script and can display phpinfo(). (It was not working before, at least when 4.1.0RC1 is released.) output.c has not been changed. It seems real problem was in some other place.What do you mean by output.c not being changed? 4.1.0RC1 and HEAD have different output.c's...
Can you try to apply the patches at http://cvs.php.net/diff.php/php4/main/output.c?ws=0&r1=1.75&r2=1.77&ty=u to 4.1.0RC1, and see if the problem goes away? It should apply cleanly, except for a meaningless $Id conflict.I tried and it *works*. Now 4.1.0RC CVS works really well so far, but more tests are needed.
The 4.0.7 codebase did not support multiple layers of internal/chunked output buffering, so mixing output buffering and mbstring-auto-encoding did not work.Usually, I don't use zlib compression. I noticed the problem when 4.0.7RC is relased. It seems zlib output compression is working now. (I'm testing with --enable-mbstr-enc-trans) -- Yasuo Ohgaki