Bug 34 - Stopping SipStack and popping TimerMessages from TimerQueue causes memory leak.
Summary: Stopping SipStack and popping TimerMessages from TimerQueue causes memory leak.
Status: NEW
Alias: None
Product: resiprocate
Classification: Unclassified
Component: stack (libresip) (show other bugs)
Version: unspecified
Hardware: All Linux
: P1 normal
Assignee: Owner of all unassigned bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-09-13 03:50 CDT by tez
Modified: 2012-09-13 03:50 CDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description tez 2012-09-13 03:50:23 CDT
Hi,
there is memory leak when using timers, which are to be returned to TU at some later time. This happens if we post to SipStack ApplicationMessage with timeout( postMs for example ) and then stop SipStack. All messages which stay at current moment in TimerQueue are to be popped( but not deleted ) and they never return to TU.