Re: [recon-devel] Memory leak

[Scott Godin <sgodin@xxxxxxxxxxxxxxx>]

I'm not aware of any leaks in SipMessage.  Keep in mind that the Stack will hold onto to some Sip Messages for a period of time (ie. until it times out a transaction), so it depends on how/when your leak detection works.  You should wait at least 32 seconds after the last transaction before triggering the memory profiling.

Scott

On Wed, Jul 8, 2009 at 9:20 PM, Julio Cabezas <jcabezas@xxxxxxxxxxxxx> wrote:

Hi Scott,

 

 

            After another test run of recon I found what may be another memory leak.  This time the offending allocation is done in the stack code.

 

            File:                 ParserContainer.hxx

            Code line:         void push_back(const T & t) { mParsers.push_back(new T(t)); }

 

            One level down the stack we find the immediate caller:

 

            File:                 Helper.cxx

            Code line:         response.header(h_Contacts).push_back(contact);

 

 

 

       As I did not detect a whole SipMessage leak I am guessing the defect is inside SipMessage code.

 

       If it is really a leak I am afraid that other objects pertaining to SipMessage may also need due destruction, although my run seemingly did not trigger their allocation and leak. It would be advisable who is maintaining stack code to make a more thorough review of SipMessage.

 

 

 

Best Regards,

Julio Cabezas,

 

_______________________________________________
recon-devel mailing list
recon-devel@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/recon-devel/