run it slower and make sure it shuts down clean.

valgrind --tool=memcheck --log-file-exactly=vg.log --leak-check=full --leak-resolution=high --show-reachable=yes /path/to/freeswitch -vg


On Wed, Sep 2, 2009 at 10:11 AM, Anthony Minessale <anthony.minessale@gmail.com> wrote:
You have to reduce the load when running valgrind.



On Wed, Sep 2, 2009 at 7:59 AM, Benedikt Fraunhofer <fraunhofer.lists.freeswitch-001@traced.net> wrote:
Hello *,

2009/8/31 Rupa Schomaker <rupa@rupa.com>:
> Isn't there a known issue with lua+sql leaking memory on some platforms?

just lua, no sql in use :)

> On Mon, Aug 31, 2009 at 8:32 AM, Brian West<brian@freeswitch.org> wrote:
>> Use valgrind.

i tried that... in the beginning valgrind segfaultet several times
with some error message that it's unable to monitor so many threads.

vg_alloc_ThreadState: no free slots available
Increase VG_N_THREADS, rebuild and try again.

valgrind: the 'impossible' happened:
  VG_N_THREADS is too low

it happeneded with 400 concurrent calls pretty soon, with 100 it took
a while, but at least it consumed half a gig of ram.

Can someone interpret the file it generated so far? i put it at

 http://ns42.ath.cx/B0GdWh/vg.log.bz2

(5k compressed, 452k uncompressed) or is there just not enough
information contained?

I'll give it another shot with 50 concurrent calls but i guess this
will take ages...

Thx in advance

 Beni.






--
Anthony Minessale II

FreeSWITCH http://www.freeswitch.org/
ClueCon http://www.cluecon.com/
Twitter: http://twitter.com/FreeSWITCH_wire

AIM: anthm
MSN:anthony_minessale@hotmail.com
GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com
IRC: irc.freenode.net #freeswitch

FreeSWITCH Developer Conference
sip:888@conference.freeswitch.org
iax:guest@conference.freeswitch.org/888
googletalk:conf+888@conference.freeswitch.org
pstn:213-799-1400