When memory stays at 50-60M without nibblebill and grows to 300M with... It's definetily a leak. valgring log is available, but there is nothing suspicious in it... Try to enable niblebill yourself. On Saturday 17 April 2010, Michael Jerris wrote:
100M may just be the memory it is really using for what it is doing and not a leak. Have you seen anything to tell you this is actually a leak? Have you run under valgrind or some similar tool to confirm?
Mike
On Apr 17, 2010, at 9:26 AM, Sergey Okhapkin wrote:
I want to utilize nibblebill features for prepaid support, but as soon as I enable nibble billing with
set nibble_rate=XXX set nibble_account=NNNNNN set enable_heartbeat_events=60
in dialplan, FS process begins to eat more and more memory, RSS grows from 23M to 100M and more after processing few thousands calls and continues to grow. If I comment out those 3 lines from dialplan, then FS RSS grows from initial 23M to 50-60M (depending on the number of concurrent calls) and stays at this value, no memory leaks.
Do anybody use mod_nibblebill?
I'm experiencing this problem with all svn versions I tried including latest git version.
_______________________________________________ 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