Prevent audio buffer flush on first track switch #7696
Merged
+52
−36
Conversation
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
github-project-automation
bot
moved this to Top priorities
in HLS.js Release Planning and Backlog
robwalch
force-pushed
the
bugfix/audio-buffer-flush-on-start-regression
branch
from
97f5e60 to
cad5793
Compare
(fixes regression introduced in #7575)
krseager
approved these changes
Jan 21, 2026
github-project-automation
bot
moved this from Top priorities
to Done
in HLS.js Release Planning and Backlog
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR will...
LEVEL_SWITCHEDevents for first playing fragment detectedWhy is this Pull Request needed?
Audio back buffer removal was being triggered on start, and
LEVEL_SWITCHEDwas not, since #7575.Are there any points in the code the reviewer needs to double check?
The "smooth switch" automated test has been flaky since #7575 was merged. I noticed that one of the failures was related to the switch happening on start, but the event not being logged by the test.
Resolves issues:
Checklist