ExoPlayer can get stuck in buffering state if a decoder only returns output buffers with shouldBeSkipped
Open
@microkatz is already working on this.
Since Jul 18, 2025.
bad media
bug
needs triage
- Dominant language
- Java
- Stars
- 3k
- Forks
- 955
- Avg merge
- 12d 14h
- Merged PRs (30d)
- 2
Description
Version
Media3 main branch
More version details
No response
Devices that reproduce the issue
All
Devices that do not reproduce the issue
N/A
Reproducible in the demo app?
Yes
Reproduction steps
Play the media send by mail with ffmpeg decoder.
The media will never start and the app stays in buffering state.
This could happen with other files and other decoders that returns enough skippable buffers.
See some discussion/analysis in https://github.com/androidx/media/issues/558.
Expected result
ExoPlayer errors with a stuck in buffering.
Actual result
ExoPlayer stays in buffering state.
Media
Will send by mail.
Bug Report
- You will email the zip file produced by
adb bugreportto android-media-github@google.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.