Help with identifying memory leak

mediasoup libraries
1

I realize that this is most likely an issue with my code, but I’m posting it here in the off-chance that this is related to the library. So feel free to close/delete the issue if it is.

After shutting down all clients, I did a heapdump of my nodeJS process and noticed that a bunch of consumers weren’t cleared out.

image
image2359×1316 347 KB

When I check the PipeTransports, I get the following:

image
image2360×1314 307 KB

I’m not very knowledgeable in reading heapdumps, but any chance this is a leak in the mediasoup Worker? Is this just a case of me not cleaning something up?

1 Like
2

You didn’t say which mediasoup version. A related leak was fixed some weeks ago, please check the CHANGELOG in the source code of mediasoup to confirm.

3

Right! Sorry, this was on mediasoup v3.6.21. I believe the related leak you’re mentioning was fixed in this release?

If you can give me steps on how to collect any relevant information you need to investigate this further, I’d be happy to run them and share the results.

4

Well, let’s say the bug was not totally fixed in 3.6.21, so here the commit that should fix it:

BTW mediasoup 3.6.23 released. Thanks for reporting.

3 Likes
5

Thank you!
Can confirm that this is fixed :slight_smile:

2 Likes