-
Notifications
You must be signed in to change notification settings - Fork 317
fix(voice): commit interrupted replies when playback start arrives after forwarding completes (avatar outputs) #1960
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
snowmaker
wants to merge
2
commits into
livekit:main
Choose a base branch
from
snowmaker:fix/avatar-deferred-playback-started-commit
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| --- | ||
| '@livekit/agents': patch | ||
| --- | ||
|
|
||
| fix(voice): commit interrupted replies when playback start is reported after audio forwarding completes (avatar outputs). `forwardAudio` no longer rejects `firstFrameFut` when forwarding finishes before the remote avatar's deferred `lk.playback_started` notification arrives — previously the interrupted reply was classified "skipped" and silently dropped from the chat context, and the agent never entered the `speaking` state. A reported non-zero playback position on interruption is now also honored as evidence of partial playback. |
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
|
devin-ai-integration[bot] marked this conversation as resolved.
|
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🟡 Event listener on the shared audio output leaks when using the "say" path with deferred playback notifications
The playback-started listener is never detached from the shared audio output (
performAudioForwardingatagents/src/voice/agent_activity.ts:2519) because thesay()code path has no finally-block cleanup to settle the pendingfirstFrameFut, so each call accumulates a stale listener.Impact: Repeated
say()calls with avatar outputs that defer playback-started notifications leak event listeners, causing gradual memory growth.Mechanism: the say() path was not updated with the new cleanup pattern
The PR changed
forwardAudio(agents/src/voice/generation.ts:952) to only rejectfirstFrameFutwhensignal?.aborted, keeping the listener attached until the future settles. It then added matching finally-block cleanup inforwardSegment(agents/src/voice/agent_activity.ts:2931-2937) andprocessOneMessage(agents/src/voice/agent_activity.ts:3503-3509) to settle any still-pendingfirstFrameFut.However, the
say()path atagents/src/voice/agent_activity.ts:2519-2557also callsperformAudioForwardingbut was not updated with the same cleanup. When forwarding completes normally (stream closes, signal not aborted),firstFrameFutstays pending and theonPlaybackStartedlistener atagents/src/voice/generation.ts:894remains attached toaudioOutputindefinitely. Before this PR,forwardAudioalways rejectedfirstFrameFuton exit, so the listener was always cleaned up.(Refers to lines 2550-2557)
Prompt for agents
Was this helpful? React with 👍 or 👎 to provide feedback.