httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 45497] Scoreboard slot leaked using MaxRequestsPerChild and thread(s) do not exit gracefully
Date Wed, 12 Aug 2009 10:56:47 GMT

--- Comment #1 from Jo Schulze <> 2009-08-12 03:56:43 PDT ---
There have been 4 new releases of Apache 2.2 in the last year, but this bug
still exists. There isn't even a discussion about the patch.

This is IMHO a very grave bug since it leaves apache unusable for production
deployment if eg. mod_php is used and there are lots of HTTP requests.

With the prefork MPM, memleaks are not a big issue, since the worker process
will be terminated sometime, thus the memory be freed. This doesn't happen with
the winnt MPM because after the request has been processed, only the thread
will terminate, thus memleake accumulate over time. I have seen apache
processes growing over 1.5 GB!

Limiting MaxRequestsPerChild would be a workaround, but this bug prevents its
use because there is a good chance that the worker process won't be restarted.

Ok you could blame mod_php (or any other apache module) for its memleaks,
however that's not the point:

1) We all know there will be memleaks here and then 
2) The Apache directive MaxRequestsPerChild does not work as documented with
the winnt MPM

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message