Which version of ffmpeg did you compile? Is this still on Debian 10? It's good to hear you found a way to resolve this although we haven't been able to replicate your fix so far. I think that combination of Jibri and the version of ffmpeg bundled with Debian Buster is the culprit of the error. I made a test recording of a whole hour and the memory usage stayed at about 3GB, with no other incident nor any warning or error in logs. I finally compiled the latest version of ffmpeg and now everything is fine. Ubuntu 16, followed the instruction on github How can I debug this kind of issue ? Possible Solution So It clearly seems to be related to the sound. If I remove every parameters related to sound in this ffmpeg command line, so removing -f alsa -thread_queue_size 4096 -i plug:cloop -acodec aac, then the memory saturation issue goes away. I have to kill ffmpeg before it saturates the memory.įfmpeg -y -v info -f x11grab -draw_mouse 0 -r 30 -s 1280x720 -thread_queue_size 4096 -i :0.0+0,0 -f alsa -thread_queue_size 4096 -i plug:bsnoop -acodec aac -strict -2 -ar 44100 -c:v libx264 -preset veryfast -maxrate 2976k -bufsize 5952k -pix_fmt yuv420p -r 30 -crf 25 -g 60 -tune zerolatency -f flv rtmp://a./live2/aaa I stopped the streaming after 15 seconds and ffmpeg was already at 40% memory.Īlso if I stop completely prosody, jicofo, jvb and jibri and if I log as a jibri user and starts ffmpeg by myself, using the command I found in log.0.txt, I get the same issue, the CPU shoot to 150% and the memory keeps growing. You can find attached the log of jibri when I tried a streaming session. It eats away all the memory very quickly. With top, I could pin the culprit: ffmpeg. On jitsi when I start a recording or a streaming session, in less than a minute the recording/stream will stop and my whole server become slow and unresponsive.

Ffmpeg download keeps stalling