Hi folks! We discovered a memory leak with using:

<@U07V9N2JYGL>/rtc-node

What we tried to do: 1. connecting a new room in nodejs, waiting for 1.5min (90s), disconnecting 2. then again connecting a new room, waiting for 1.5min, disconnecting 3. then again same process.... overtime we see an increasing memory usage. this is all we deployed to google cloud run: https://github.com/us-asad/livekit-only-connect-w-settimeout-gcp/blob/main/src/index.ts

Hi @refined-appointment-81829! I hope you are doing well 🙂. We are pretty concerned with the way AudioSource is behaving. Have you folks experienced anything like this? Do you have any suggestion in which direction we are supposed to dig in?

@alert-easter-19258 isn't there anyone to check this problem at all, I think it's very critical library level problem ?

I've not seen any reports like this and I quite a few folks are using this. Were you able to see in the code base what may cause the "memory leak"? Do you have any step by step directions for how to run your code and test?

just deploy the service to google cloud run and check after ~5hrs, you'll see growing memory overtime, it's just 58 lines of code, a simple express app, nothing much to explain