DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=44026>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=44026 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO ------- Additional Comments From [EMAIL PROTECTED] 2007-12-13 06:38 ------- OK. Then we need to do it the hard way :-(. Please apply the patch I attach in a few minutes (which only add a few apr_pool_tag calls which will also remain in production code) and execute configure with the following CFLAGS set: CFLAGS="-O2 -g -Wall -DAPR_POOL_DEBUG=16" and recompile your httpd. This creates a log message for every pool allocation in stderr which is your terminal during startup and your main error_log file after detachment. Lines look like the following: POOL DEBUG: [20233/1094719840] PALLOC ( 20289/ 20289/ 329106) 0x552a c86ed0 "proxy_conn_scpool" <buckets/apr_brigade.c:61> (46/46/1) So it would be good if you could grep your logfile for "POOL DEBUG" after you reached 10G memory consumption. To be honest I do not know how large your error log gets until this and if this is technically feasible in your environment. If the result is too large even in compressed form we need to discuss further preaggregations before you can attach the results here. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
