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

[reSIProcate-users] Memory leak during ServerInviteSession::accept()


I see the following from Valgrind as possible memory leak. I’m using Resiprocate 1.4 (For every call, there is a leak of 68 Bytes). Call does get connected withouot issues and ends gracefully.

 

==26284== 3,400 bytes in 50 blocks are still reachable in loss record 706 of 716

==26284==    at 0x4004790: operator new(unsigned) (vg_replace_malloc.c:164)

==26284==    by 0x825F80A: resip::DumTimeout::clone() const (in /opt/vapp/bin/msgserver_May29_5)

==26284==    by 0x834B8DC: resip::SipStack::postMS(resip::ApplicationMessage const&, unsigned, resip::TransactionUser*) (in /opt/vapp/bin/msgserver_May29_5)

==26284==    by 0x824428F: resip::DialogUsageManager::addTimer(resip::DumTimeout::Type, unsigned long, resip::Handle<resip::BaseUsage>, unsigned, unsigned) (in /opt/vapp/bin/msgserver_May29_5)

==26284==    by 0x8275C00: resip::InviteSession::handleSessionTimerRequest(resip::SipMessage&, resip::SipMessage const&) (in /opt/vapp/bin/msgserver_May29_5)

==26284==    by 0x8292FFD: resip::ServerInviteSession::sendAccept(int, resip::Contents*) (in /opt/vapp/bin/msgserver_May29_5)

==26284==    by 0x8293443: resip::ServerInviteSession::accept(int) (in /opt/vapp/bin/msgserver_May29_5)

==26284==    by 0x80E5F90: pp::ResipDialogHandler::OnMSPPAddConnectionResp(msg::msppAddConnectionResp*) (ResipDialogHandler.cxx:1929)

==26284==    by 0x8105568: pp::ResipDialogHandler::processAppCommand(comm::Message*) (ResipDialogHandler.cxx:3496)

==26284==    by 0x80B59A5: pp::AppCommand::executeCommand() (ResipAppCommands.cxx:18)

==26284==    by 0x8258227: resip::DialogUsageManager::internalProcess(std::auto_ptr<resip::Message>) (in /opt/vapp/bin/msgserver_May29_5)

==26284==    by 0x82583BA: resip::DialogUsageManager::process(int, resip::RWMutex*) (in /opt/vapp/bin/msgserver_May29_5)

 

Thanks,

Vasanthi