You are viewing a plain text version of this content. The canonical link for it is here.

Posted to bugs@httpd.apache.org by bu...@apache.org on 2002/09/05 00:23:41 UTC

DO NOT REPLY [Bug 12320] New: - ap_get_client_block memory hog

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12320>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12320

ap_get_client_block memory hog

           Summary: ap_get_client_block memory hog
           Product: Apache httpd-2.0
           Version: 2.0.40
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Core
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: eider@bol.com.br


in 2.0.40, ap_get_client_block seems to be broken. If 
you use webdav and want to put a large file (200MB), you 
will se the web server going bigger and bigger, as if 
there is a memory leak. In fact, the brigade function allocates a chunk of 
memory for each block and doesn't deallocate it until the client drops 
connection. This is a unpleaseant feature for big files.

   I got the 2.0.39 one into the 2.0.40 http_protocol.c 
file and everything gots better.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org