# Was there any noted memory leak between version 3.10.8 and recent?

**URL:** <https://mediasoup.discourse.group/t/was-there-any-noted-memory-leak-between-version-3-10-8-and-recent/5164>\
**Category:** Off Topic\
**Created:** [April 17, 2023, 8:02pm UTC](https://mediasoup.discourse.group/t/was-there-any-noted-memory-leak-between-version-3-10-8-and-recent/5164 "2023-04-17T20:02:07Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![BronzedBroth](https://avatars.discourse-cdn.com/v4/letter/b/ad7895/32.png) [@BronzedBroth](https://mediasoup.discourse.group/u/BronzedBroth)\
**Post date:** [April 17, 2023, 8:02pm UTC](https://mediasoup.discourse.group/t/was-there-any-noted-memory-leak-between-version-3-10-8-and-recent/5164/1 "2023-04-17T20:02:07Z")

</div>

Seeing workers use 3-8GB of ram which is exceedingly high, I normally see them a couple hundred MB or less.

This has never happened before so I can’t replicate it just yet.

It’s affecting my consumer servers mostly, which those servers will take a produced tracks over PipeTransport and consume it for many viewers. I don’t see this problem on the producer server which suggests that consuming and producing aren’t the true cause for this ramp-up potentially but may be (consumer servers can open 1-1,000+ transports in a matter of seconds and clear immediately depending on room size and people entering/leaving rooms)

Would be curious if this has anything to do with PipeTransport and retransmission. Last week and a half servers had just started having major latency issues; 90ms average but every 10-30 seconds a 1,000-3,000ms increase. Thinking this may be slowly adding up over-time or something isn’t clearing from memory.

* * *

Open to ideas to test this locally and report findings.

---

<div class="post-metadata">

**Author:** ![vuzya](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/vuzya/32/2472_2.png) [@vuzya](https://mediasoup.discourse.group/u/vuzya)\
**Post date:** [December 19, 2023, 1:32pm UTC](https://mediasoup.discourse.group/t/was-there-any-noted-memory-leak-between-version-3-10-8-and-recent/5164/2 "2023-12-19T13:32:17Z")

</div>

Does this problem still exist for you?

---

<div class="post-metadata">

**Author:** ![BronzedBroth](https://avatars.discourse-cdn.com/v4/letter/b/ad7895/32.png) [@BronzedBroth](https://mediasoup.discourse.group/u/BronzedBroth)\
**Post date:** [December 19, 2023, 10:48pm UTC](https://mediasoup.discourse.group/t/was-there-any-noted-memory-leak-between-version-3-10-8-and-recent/5164/3 "2023-12-19T22:48:36Z")

</div>

I could only assume that it was related to pipe-transport re-transmission. When a few servers were having network delay the buffer continued to grow. That’d be my guess, it now sits around 1GB for 4vCores when running properly.

I haven’t developed for a while so I can’t confirm how garbage collection works with mediasoup if it ever cleared until restarting the service.