On Thu, Jan 10, 2008 at 08:18:54PM -0600, Graham Frank wrote: > We actually have the MaxRequestsPerChild set to 1000 and KeepAlive off.
That means the leak is more than 100KB per request on average, although it could be one very bad leak :/ > Know of any way that we could find the leak considering the vastness of all > the possibilities? Unfortunately this isn't so simple, it requires actually debugging the code. You can use a tracer or debugger attached to one of the children to try and determine which requests trigger the leak. Another less involved way might be to replay the access log against another instance of apache, line by line (or perform a binary search, splitting the requests in half progressively) and checking the RSS each time. -- Colm MacCárthaigh Public Key: [EMAIL PROTECTED] --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: [EMAIL PROTECTED] " from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
