|Component:||All||Assignee:||Apache HTTPD Bugs Mailing List <bugs>|
Description tommyng2009 2011-05-16 06:49:27 UTC
we and many other HTTPD fellows have suffered greatly from this leak. You can see the full detail in this link http://www.lydonchandra.com/content/hunting-memory-leak-apache-httpd-module#comment-2180 Please fix it as soon as possible as I have to hang production once in a while just to restart the server. Restarting or stopping/starting HTTPD process would not fix the problem Thanks!
Comment 1 Eric Covener 2011-05-16 10:53:32 UTC
You'll have to provide concrete details in the bug report. Furthermore, If the leak requires a modified third-party module, it's not clear what kind of relief you'll find in the ASF bugzilla, so you should reproduce without it.
Comment 2 Christophe JAILLET 2012-04-21 06:57:35 UTC
When following the link, we arrive on a blog where is written: " The error was coming from one of our own Apache modules by lydonchandra - 02/23/2012 - 16:51 The error was coming from one of our own Apache modules, we forgot to delete win32 handles, and this accumulates over time. " So I think that this bug report should be closed definitively.