[reSIProcate] RE: memory leak in timerqueue.cxx ?

[Scott Godin]

You likely need to run your process loop for approx. 32 seconds before you
let your program shutdown, in order for the transaction timers to expire and
be deleted.

-----Original Message-----
From: Justin Matthews [mailto:justin.matthews at ivr.com] 
Sent: Saturday, June 25, 2005 1:17 PM
To: resiprocate-devel at list.sipfoundry.org
Subject: [reSIProcate] RE: memory leak in timerqueue.cxx ?

After looking at the code I realized that the mFifo is a reference to a fifo
in the TransactionController and is in use. 

I was unable to find the location of the leak, but the scenario I described
below should reproduce the problem.  Please let me know if you need any
additional details about the scenario.

Thanks,

-Justin

-----Original Message-----
From: Justin Matthews [mailto:justin.matthews at ivr.com] 
Sent: Saturday, June 25, 2005 9:13 AM
To: 'resiprocate-devel at list.sipfoundry.org'
Subject: memory leak in timerqueue.cxx ?

Hello,

My debug tools are showing a memory leak in timerqueue.cxx:152

"mFifo.add(new TimerMessage(i->mTransactionId, i->mType, i->mDuration));"

mFifo does not appear to be used anywhere else in the code so objects are
never used from this fifo, from what I can see anyway.

The full call stack is:

Resip::TimerQueue::process line 152
Resip::TransactionController::process line 81
Resip::SipStack::process line 420

Also, the scenario I was running used DUM and rejected all incoming INVITE's
with a 480 using ServerInvitesession::reject(480).


Thanks,

-Justin

_______________________________________________
resiprocate-devel mailing list
resiprocate-devel at list.sipfoundry.org
https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel