On 6/30/06, Garrett Rooney <[EMAIL PROTECTED]> wrote:
If you look at apr_thread_create, you'll see that each call to it creates a new subpool inside the pool you pass. That seems likely to be the cause of your memory usage...
That's a good point - I didn't realise that. [After spending some time looking at the source code...] That pool is destroyed in apr_thread_exist and apr_pool_destory is smart enough to remove the thread-specific pool from the parent's child list. -- Ivan Ristic, Technical Director Thinking Stone, http://www.thinkingstone.com ModSecurity: Open source Web Application Firewall
