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=26799>. 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=26799 httpd process grows rapidly to > 1GB until server runs out of swap ------- Additional Comments From [EMAIL PROTECTED] 2004-02-20 19:56 ------- The ulimit commands are working. When an httpd process tries to rapidly increase its memory usage it generates a SEGV and core dumps before it starves the server of both physical and virtual memory. I now have six 230MB httpd process core files. Analyzing the core file shows which thread failed during an allocation and caused the SEGV but that thread necessarily isn't the one causing the problem, it is just the thread which had the memory allocation failure. What I need to find is the request and the thread which was allocating all the memory. Is there any easy way to get this data from each thread/request? Perhaps in the apr_pool data somewhere? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
