Re: Memory leak in nist implementation

When the tx times out delete the dialog and then you have to wait for
the garbage collection to run before you check for leak.

Ranga.

On Mon, Jun 30, 2008 at 2:32 PM, Francisco Javier Tellez Vaquero
<[email protected]> wrote:
> Hi Ranga,
> I agree the example case is a listener bug, but think the opposite case=
:
>
>   - You send a BYE request but no response is received.
>
> You have no control about this point, so the idea is trying to close th=
e
> dialog anyway.
>
> BR.
>
>
>> Date: Mon, 30 Jun 2008 14:09:05 -0400
>> From: [email protected]
>> To: [email protected]
>> Subject: Re: [nist-sip] Memory leak in nist implementation
>> CC: [email protected]
>>
>> On Mon, Jun 30, 2008 at 1:55 PM, Francisco Javier Tellez Vaquero
>> <[email protected]> wrote:
>> > Hi all,
>> > I see sometimes not all stack objects are destroyed.
>> >
>> > For example, if you receive BYE request but no 200 response is sent,
>> > dialog
>> > is never closed. There're a lot of different cases (ACK's lost, ...).
>>
>> Not sending a 200 OK to a BYE is an application bug. Please fix that.
>>
>> Please post a specific test case (without listener bugs) and I can loo=
k
>> into it.
>>
>> Ranga
>>
>> >
>> > I have tried to free memory executing 'terminate()' and/or 'delete()=
'
>> > methods in both transaction and dialog objects but without any resul=
t.
>> >
>> > Is there any way to force to free these objects (timers, dialogs,
>> > transactions, ...) ?
>> >
>> > Regards.
>> >
>> >
>> >
>> > ________________________________
>> > Tecnolog=EDa, moda, motor, viajes,.suscr=EDbete a nuestros boletines=
 para
>> > estar
>> > siempre a la =FAltima MSN Newsletters
>> > _______________________________________________
>> > nist-sip mailing list
>> > [email protected]
>> > http://www-x.antd.nist.gov/mailman/listinfo/nist-sip
>> >
>> >
>>
>>
>>
>> --
>> M. Ranganathan
>
> ________________________________
> Sigue los principales acontecimientos deportivos en directo. MSN Motor



--=20
M. Ranganathan