Re: [reSIProcate-users] Memory Leak

[kaiduan xie <kaiduanx@xxxxxxxx>]

If you use Linux, try running under valgrind and gracefull shutdown your application, you will be able to spot the memory leak easily.

                                                                      ^^^^^^^

 

/Kaiduan

---

From: Francis Joanis <francis.joanis@xxxxxxxxx>
To: gregory <gregory@xxxxxxxx>
Cc: "resiprocate-users@xxxxxxxxxxxxxxx" <resiprocate-users@xxxxxxxxxxxxxxx>
Sent: Thu, November 18, 2010 9:05:40 AM
Subject: Re: [reSIProcate-users] Memory Leak

Hi Gregory,

Are you using the SipStack directly or are you using the DUM? Would you be able to post some examples of your code?

Thanks,

Francis

Le 2010-11-18 à 08:56, gregory <gregory@xxxxxxxx> a écrit :

Hi,

 

I'm running a test application with the following scenario:

 

1. A sends INVITE to B.

2. B accepts the INVITE, so the call is connected.

3. After a few seconds, B sends BYE to A.

4. Goto 1

 

The problem is that the memory consumption of my process constantly grows.

I noticed that the memory sometimes grows after calling and after the call is terminated, it's not always reduced to what it was before the call.

What can be the problem?

I found posts online about memory leaks in Resiprocate, but didn't find what I can do in order to avoid them.

 

Thanks

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