Startup failure/freeze when additional discontinuity tags in alternate audio/text tracks
@marcbaechinger is already working on this.
Since Apr 17, 2023.
- Dominant language
- Java
- Stars
- 3k
- Forks
- 955
- Avg merge
- 12d 14h
- Merged PRs (30d)
- 2
Description
Media3 Version
ExoPlayer 2.17.1
Devices that reproduce the issue
All devices
Devices that do not reproduce the issue
No response
Reproducible in the demo app?
No
Reproduction steps
Configure the player to disallow chunkless startup: setAllowChunklessPreparation(false)
Details
Media must contain a track that that has isMasterTimestampSource set to false during the preparation step and contains 1 or more additional #EXT-X-DISCONTINUITY tags before the first sample chunk.
This scenario causes the timestampAdjuster provided for that discontinuity sequence to be provided for only to a single track. That HlsMediaChunk is unable to initialize the timestampAdjuster causing the call : timestampAdjuster.sharedInitializeOrWait(isMasterTimestampSource, startTimeUs); to block loading until the timestampAdjuster initialization can be completed.
Since no other tracks contain the same discontinuity sequence and will not be provided with the same timestampAdjuster as the waiting HlsMediaChunk's - loading will never complete.
Expected result
Playback starts
Actual result
Playback is stuck in loading state
Media
https://storage.googleapis.com/mlbapp-streaming-resources/big_buck_bunny_disc/x36xhzz.m3u8
Bug Report
- You will email the zip file produced by
adb bugreportto dev.exoplayer@gmail.com after filing this issue.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.