Doesn't that look like a pool that isn't being destroyed? On Fri, Sep 4, 2009 at 9:10 AM, Rupa Schomaker<rupa@rupa.com> wrote:
Worst offenders (leakers over 100K). The last one is the worst (672M) -- looks like a lua script. What are you doing in lua again? ==28624== 672,268,288 bytes in 82,064 blocks are still reachable in loss record 529 of 529 ==28624== at 0x4022AB8: malloc (vg_replace_malloc.c:207) ==28624== by 0x410BB2F: apr_pool_create_ex (apr_pools.c:300) ==28624== by 0x4111176: apr_thread_create (thread.c:171) ==28624== by 0x4080878: switch_thread_create (switch_apr.c:631) ==28624== by 0x6C278E9: lua_thread (mod_lua.cpp:372) ==28624== by 0x6C27948: ??? (mod_lua.cpp:407) ==28624== by 0x40AADFC: switch_api_execute (switch_loadable_module.c:1567) ==28624== by 0x583A7FC: ??? (mod_commands.c:2426) ==28624== by 0x40A8881: switch_scheduler_execute (switch_scheduler.c:61) ==28624== by 0x40A8DE0: task_thread_loop (switch_scheduler.c:127) ==28624== by 0x40A8EA3: switch_scheduler_task_thread (switch_scheduler.c:168) ==28624== by 0x4110E05: dummy_worker (thread.c:138) ==28624== ==28624== LEAK SUMMARY: ==28624== definitely lost: 63,113,740 bytes in 1,690,880 blocks. ==28624== indirectly lost: 35,632 bytes in 491 blocks. ==28624== possibly lost: 645,758 bytes in 9,150 blocks. ==28624== still reachable: 681,849,684 bytes in 113,077 blocks. ==28624== suppressed: 0 bytes in 0 blocks.
-- -Rupa