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 2003/05/24 19:43:55 UTC

DO NOT REPLY [Bug 19078] - Possible memory leak with httpd 1.3.26 core

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=19078>.
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=19078

Possible memory leak with httpd 1.3.26 core

slive@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID



------- Additional Comments From slive@apache.org  2003-05-24 17:43 -------
No, in general, most OSes don't let processes release memory back to the OS
until they are finished.

In general, for us to debug this, we would need much more specific information
about what is going on.  I see no real reason to suspect apache is leaking
memory from the infromation you've given.

See the MaxRequestsPerChild directive for a general way to deal with resource
leaks.

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