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=44402>. 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=44402 ------- Additional Comments From [EMAIL PROTECTED] 2008-02-12 17:14 ------- I tried to debug the crash =>[1] allocator_free(allocator = 0x101f870, node = (nil)), line 331 in "apr_pools.c" [2] apr_pool_clear(pool = 0x102fb88), line 710 in "apr_pools.c" [3] ap_core_output_filter(f = 0x1020550, b = 0x101f9e8), line 899 in "core_filters.c" In ap_core_output_filter, crash is happening when apr_pool_clear is called for deferred_write_pool. apr_pool_clear(ctx->deferred_write_pool); On further investigation, I found that for ctx->deferred_write_pool, pool->ref points to pool->next i.e pool->ref == &pool->next Thus in apr_pool_clear : if (active->next == active) return; *active->ref = NULL; // ---> this cause active->next to set to NULL because // active->ref points to active->next allocator_free(pool->allocator, active->next); The situation doesn't arrive on normal single connection situation. This happens only under stress. Under normal connection active->next == active and function returns from apr_pool_clear (when called for ctx->deferred_write_pool) -- 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]
