reSIProcate

Mailing Lists

Source Code

Google Search:



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

Re: [reSIProcate-users] makeOutOfDialogRequest memory leak ?

When you call makeOutOfDialogRequest, DUM internally creates Creator, DialogSet, and AppDialogSet objects - these objects also create many other objects.  These enable DUM to be able to properly track the responses as they come in.  The objects will eventually be destroyed after the final response arrives.  Some of the objects (ie. entry in the MergeRequest detection map) - are cleaned up based on a timer (I think something like 32 seconds after sending the request).

Scott

On Mon, Sep 26, 2011 at 4:08 PM, Bruno Keymolen <Bruno.Keymolen@xxxxxxxxxx> wrote:

Hi,

 

Can someone explain me why the following loop will end up eating all the memory ?

 

for(int x=0;x<1000000;x++){

resip::SharedPtr<resip::SipMessage> epMsg = dum->makeOutOfDialogRequest(to, resip::MESSAGE, 0);

epMsg.reset();

}

 

 

Thanks,

 

Bruno Keymolen

 

 


_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/