hi Costa:
       I have a rough read apr memory pool source code,I have know modsecurity how to handle memory management.
       I try to modfied main.cpp(standalone/man.cpp) in my Multi thread program that is similar to  apache's fuction!
       but my program have serious memory leak, I'm sure use apr_pool_destroy(r->connection->pool) function when            per session need free!
       I have one question.does modsecurity  support multi thread?
------------------ 原始邮件 ------------------
发件人: "Felipe Costa";<FCosta@trustwave.com>;
发送时间: 2014年7月8日(星期二) 上午7:18
收件人: "mod-security-developers@lists.sourceforge.net"<mod-security-developers@lists.sourceforge.net>;
主题: Re: [Mod-security-developers] help me!pls

Hi Jarwin,

ModSecurity uses this Apr Memory Pool to handle the memory management, for further information:
 - http://en.wikipedia.org/wiki/Apache_Portable_Runtime
 - http://www.apachetutor.org/dev/pools

Felipe "Zimmerle" Costa
Security Researcher, SpiderLabs


From: 蕴涵 <252805232@qq.com>
Reply-To: "mod-security-developers@lists.sourceforge.net" <mod-security-developers@lists.sourceforge.net>
Date: Tuesday, July 1, 2014 12:47 PM
To: mod-security-developers <mod-security-developers@lists.sourceforge.net>
Subject: [Mod-security-developers] help me!pls

     I ran into a problem when read modsecurity-2.7.7 source code,when http request came,modsecurity will executive function(create_tx_context()),In this fuction call
apr_allocator_create(&allocator),but I cann't find any apr_allocator_free() fuction or apr_allocator_destroy() function to release allocator memory,The program will not cause memory leaks? if not,when does modsecurity  release memory? I can not sleep wellbecause of this puzzle problem!pls reply me!!


This transmission may contain information that is privileged, confidential, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is strictly prohibited. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format.