I deployed an update to our self hosted agents today updating the

@livekit/*

packages from

v1.0.15

to

v1.0.22

and now we are seeing a major memory leak. I will be bisecting the changes tomorrow to try to narrow down which livekit package update introduces the issue… AgentSession is configured with: • vad:

silero.VAD

• stt:

inference.STT

with

"deepgram/nova-3"

as the model • llm: aws bedrock (custom plugin that is vetted) • tts:

elevenlabs.TTS

• turnDetection:

livekit.turnDetector.MultilingualModel

That's still quite an old version of Agents though? (From May this year). I haven't gone through to find instances of leaks reported between 1.0.15 and 1.0.22, and subsequently fixed, but is there a reason to specifically move to 1.0.22

This for agents-js. 1.0.15 was from a month ago (source)

Yeah @lively-winter-88668 just a heads up, this was in reference to the JS package! I believe @bitter-ghost-46918 was helping us previously as we integrated, but it looks he might be out. Is there anyone else on the team that might be able to weigh in on the JS side?

WIP pr to fix a couple leaks - https://github.com/livekit/agents-js/pull/875

> I believe @bitter-ghost-46918 was helping us previously as we integrated, but it looks he might be out. Hey @numerous-easter-60982 I'm still actively working on JS side, but currently in China time zone. Feel free to ask me anything!

Great, thanks for the update & PR and thanks Brian for jumping in.