httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 23567] - Huge memory usage
Date Mon, 20 Oct 2003 10:58:42 GMT
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=23567>.
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=23567

Huge memory usage





------- Additional Comments From trawick@apache.org  2003-10-20 10:58 -------
I spent some time last week-end investigating this.  Hopefully this info can
help whoever has time to look for a solution.

The only memory leak I was able to find is caused by an endless number of
cleanups registered against the request pool by content-length filter and then
killed by the core output filter.  A cleanup is registered during
apr_brigade_split(), as the content-length filter separates out the data already
read from the CGI in order to send it to the client.  When the content-length
filter is able to read a bit more from the CGI, the same thing happens again.

This same pattern could occur with most any other filter.  Other filter code
that could do the pipe bucket read is going to have to do the same thing --
brigade-split and pass-brigade -- before waiting for more output from the CGI.

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


Mime
View raw message