< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index  

RE: [reSIProcate] Memory leak in TransactionState.cxx


I checked in a fix for this.  I also made a few other changes to ensure that
mMsgToRetrasmit is always deleted before it is set - to avoid other memory
leaks.

Thanks Kaiduan!


-----Original Message-----
From: kaiduan xie [mailto:kaiduanx@xxxxxxxx] 
Sent: Monday, December 20, 2004 2:07 PM
To: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
Subject: [reSIProcate] Memory leak in TransactionState.cxx

Hi,

Caught a memory leak in
TransactionState::processClientInvite()

    else if (mState == Completed)
    {
   // Any retransmissions of the final response that
   // are received while in the "Completed" state MUST
   // cause the ACK to be re-passed to the transport
   // layer for retransmission.
   assert
(mMsgToRetransmit->header(h_RequestLine).getMethod()
== ACK);
    sendToWire(mMsgToRetransmit, true);
    delete msg; //xkd-2004-12-20
    }

Merry Christmas and Happy New year to all members of
resiprocate community.

Best regards,

kaiduan

______________________________________________________________________ 
Post your free ad now! http://personals.yahoo.ca
_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxxxxxx
https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel