-
Notifications
You must be signed in to change notification settings - Fork 6k
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
NPE in ExtractorMediaSource #3796
Comments
Thanks for reporting. This is a bug caused by removing a currently playing or loading child We already have a fix which will be pushed to the dev-branch soon. |
This could happen when a media source is removed from a DynamicConcatenatingMediaSource and one of its media periods is still active. This media period is only removed by the player after the player received a timeline update and thus we shouldn't release the removed child source as long as it has active media periods. Issue:#3796 ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=184522836
Closing because issue is fixed on the dev branch. |
This could happen when a media source is removed from a DynamicConcatenatingMediaSource and one of its media periods is still active. This media period is only removed by the player after the player received a timeline update and thus we shouldn't release the removed child source as long as it has active media periods. Issue:#3796 ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=184522836
Stack trace:
This happened randomly when playing a new queue in my music player app. I wasn't doing anything different than usual, but here is the relevant code, slightly edited for clarity, that was executing at the time:
dynamicSource
is aDynamicConcatenatingMediaSource
.sourceFromTrack
returns anExtractorMediaSource
based on aMediaSource
that tails from aRandomAccessFile
.This was tested on a Pixel 2 XL running 8.0.1 with ExoPlayer 2.6.1. I've tested the app hundreds of times and never seen this issue before so I cannot reproduce it. It appears that this is the same as #1914 but that issue is closed.
The text was updated successfully, but these errors were encountered: