You have to reduce the load when running valgrind.
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 :)
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.
_______________________________________________
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org