[reSIProcate] memory leak on ServerPublication.

[Derek MacDonald]

That should probably be reset, not release.I'll look into it.

 

Thanks, 

 

Derek

 

CONFIDENTIALITY NOTICE

This email and any files transmitted with it contains proprietary
information and, unless expressly stated otherwise, all contents and
attachments are confidential. This email is intended for the addressee(s)
only and access by anyone else is unauthorized. If you are not an addressee,
any disclosure, distribution, printing or copying of the contents of this
email or its attachments, or any action taken in reliance on it, is
unauthorized and may be unlawful. If you are not an addressee, please inform
the sender immediately and then delete this email and any copies of it.
Thank you for your co-operation.

  _____  

From: resiprocate-devel-bounces at list.sipfoundry.org
[mailto:resiprocate-devel-bounces at list.sipfoundry.org] On Behalf Of Noiile
Sent: Thursday, November 24, 2005 8:57 PM
To: resiprocate-devel
Subject: [reSIProcate] memory leak on ServerPublication.

 

resiprocate-devel, Hello 

 

In code ServerPublication::updateMatchingSubscriptions(), ServerPublication
release the ownership of mLastBody.mContents and  mLastBody.mAttributes.

I don't understand why do it like this, and I found that it will result in
memory leaks because no one will delete object mContents and mAttributes,
ServerPublication lost the ownership of them.

 

ServerPublication::updateMatchingSubscriptions()

{

   ........

   //Noiile:MEMORY LEAKS!!!

   //mLastBody.mContents.release(); 
   //mLastBody.mAttributes.release();

}

 

Noiile,
<mailto:%3c!--AID_FROMADDRESS_BEGIN--%3enoiile at hotmail.com%3c!--AID_FROMADDR
ESS_END--%3e> noiile at hotmail.com

2005-11-25 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20051125/8dfde203/attachment.htm>