Memory leak about mediasoup

[jmillan]

Which memory is not released, the one of mediasoup-worker process?

The fact that malloc does not release the memory to the system does not necessarily mean that the is a memory leak.

Have you tried using jemalloc instead?

[ibc]

I'm afraid we cannot accept memory leak bug reports that are based on full apps or demo apps and do not precisely point to the exact memory leak. We do run mediasoup with Valgrind and we are not aware of memory leaks.

Another story is that, due to how malloc works, in some cases it takes long for the no longer used memory to be released as Jose said in comment above.

[runner365]

I'am sorry that I didn't find:

export MEDIASOUP_USE_VALGRIND="true"
export MEDIASOUP_VALGRIND_OPTIONS=${MEDIASOUP_VALGRIND_OPTIONS:="--leak-check=full --track-fds=yes --log-file=./mediasoup_valgrind_%p.log"}

It can use valgrind to check memory leak.

so you said it cause by the system malloc, which will release slowly back to the system.
Thanks, I will check whether they can be released back to system.
And use valgrind to test them.

[ibc]

As Jose said above, using jemalloc mitigates the problem. We use it in production.

[runner365]

jemalloc

Thanks, we will try it.
we develop sfu server based on mediasoup-demo which is nodejs. we see you has developed rust interface api in mediasoup.
Do you use rust in production and discard the nodejs?

[ibc]

Do you use rust in production and discard the nodejs?

We are not discarding NodeJS at all. We use it in production and others use Rust.