When it comes to memory leaks you need to use ASAN (or valgrind). apt-get install libasan5 cd freeswitch ./configure --enable-address-sanitizer --enable-pool-sanitizer && make install export LD_PRELOAD=/usr/lib/gcc/x86_64-linux-gnu/8/libasan.so export ASAN_OPTIONS=verbosity=1 /usr/local/freeswitch/bin/freeswitch -nf -vg -core Run some call scenarios you suspect lead to mem leaks and then shut down FS, you'll see the ASAN output at shutdown. On Mon, Feb 8, 2021 at 10:54 PM <edson@inoutglobal.xyz> wrote:
Dears,
Is it possible to find out what Freeswitch’s task leads operation system run out of memory?
It causes OS to start OOM Killer.
1-This is a backtrace Log output.
2-dmesg output showing OOM killer in action.
[1385455.947689] Out of memory: Kill process 21698 (freeswitch) score 834 or sacrifice child
[1385455.956673] Killed process 21698 (freeswitch) total-vm:12718944kB, anon-rss:8202856kB, file-rss:0kB, shmem-rss:0kB
Regards,
Edson _________________________________________________________________________
The FreeSWITCH project is sponsored by SignalWire https://signalwire.com Enhance your FreeSWITCH install with disruptive priced SMS and PSTN services. Build your next product on our scalable cloud platform.
Join our online community to chat in real time https://signalwire.community
Professional FreeSWITCH Services sales@freeswitch.com https://freeswitch.com
Official FreeSWITCH Sites https://freeswitch.com/oss https://freeswitch.org/confluence https://cluecon.com
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 https://freeswitch.com