Artemii Sergeev

I guess why memory can be eaten. When the kms falls, it starts to create a core dump and therefore begins to eat up memory. These are just my guesses.

Our another kurento was crashed yesterday. Dump file didn't create but I have some logs. Maybe it will helps ```Jul 2 17:09:39 kms11 b5bbd8291fc3[1382]: 14:44:08.546063019 1 0x7f06202514a0 WARN rtpsource rtpsource.c:1147:update_receiver_stats:...

One more crush on low load service ( ``` Aug 3 10:30:22 kms16 8108644a900d[1329]: 8:04:47.159301192 1 0x7f3464280de0 WARN rtpsource rtpsource.c:1147:update_receiver_stats: duplicate or reordered packet (seqnr 13690, expected 13702) Aug 3...

An another one: ``` (gdb) bt #0 0x00007f41f616c1a6 in __GI_abort () at abort.c:125 #1 0x00005599c56c6769 in Debug::DeathHandler::SignalHandler(int, void*, void*) () at /build/server/death_handler.cpp:299 #2 0x00005599c56c6769 in Debug::DeathHandler::SignalHandler(int, void*, void*) (sig=, secret=)...

@j1elo Where can I see to use of the method? We connect to the kurento server through our node.js kurento-client. It was forked and rewritten from https://github.com/Kurento/kurento-tutorial-node/tree/master/kurento-one2one-call with using socket.io...

There a lot of one2one pair of clients connected (10-70 pair). Different geographic areas. Load doesn't matter. This does not happen often