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

[reSIProcate] Memory leak when using Asynch challenge decision


ServerAuthManager doesn't release message which waits to be decided to 
challenge it or not.
Specifically, when user returns Async from requiresChallenge() handler, message 
in question is put to mMessages map and handle() returns EventTaken. Than, when 
it gets ChallengeInfo regarding this message, it removes it from map 
immediately, but than doesn't release the message itself in two cases: when 
challenge is failed and is required. If challenge is not required it re-posts 
message and i don't exactly know it's final destiny.
I would suggest to change Line 67 of ServerAuthManager.cxx from
      SipMessage* sipMsg = it->second;
to
      auto_ptr<SipMessage> sipMsg( it->second );
It works for me, memory leak is gone.

Best regards,

Arthur Moroz
Lead Software Developer
3CX  - http://www.3cx.com




__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com