@jzs175 from my experience:
if 5 people on the room, jibri will receive 5 video stream,
if 10 people on the room, jibri will receive 10 video stream,
if 25 people on the room, jibri will receive 25 video stream
and so on…
Jibri will have to decode the video all at once, record them, and then save them to a file.
That decode job is done by the chrome. It using much cpu & ram. This is actually happened to us too. Our browser will consume more CPU & RAM when we have more participant in the room.
The record & save to a file job is done by ffmpeg, this process using much cpu, but for some reason it makes the memory leaking if the cpu is not strong enough.
So, in your case, the cpu is already busy to handle the decoding, and there is not much left to handle the recording, that is why the memory is leaking. the solution is one of these 2:
downgrade the jibri, your version of jibri record in FHD resolution. that consume much cpu, I use jibri version 8.0-14-g0ccc3f6-1. by default it recording in HD resolution. It will reduce the CPU consumptions when recording. Or you can build your own jibri from source code and change the recording resolution by your self.
give jibri more cpu to handle the recording. how much? sorry but i don’t know either, you have to test it yourself.