Fix the memory leak of Google STT when no audio input.#5591
Open
jmuk wants to merge 1 commit intolivekit:mainfrom
Open
Fix the memory leak of Google STT when no audio input.#5591jmuk wants to merge 1 commit intolivekit:mainfrom
jmuk wants to merge 1 commit intolivekit:mainfrom
Conversation
When the RTC session is idle without any audio input, Google STT re-create the client object and re-connect periodically. However some old resources actually remain as they're not cancelled properly, causing memory leak. This PR adds the clean-up of such scenarios. With this change, I confirmed my experience of the memory leak is gone. Fixes livekit#5590
|
|
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When the RTC session is idle without any audio input, Google STT re-create the client object and re-connect periodically. However some old resources actually remain as they're not cancelled properly, causing memory leak.
This PR adds the clean-up of such scenarios. With this change, I confirmed my experience of the memory leak is gone.
Fixes #5590