-
Notifications
You must be signed in to change notification settings - Fork 126
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
IllegalStateException sometimes happens when playing Dash streams #70
Comments
Thanks for reporting! Looks like this tends to happen on faster manycore devices. I have no idea how to reproduce this yet, but I think the problem lies within the |
Do you use the |
I'm using I'm using retrofit to load the MPD and an The only other
which happens right before |
Operating on the global reference led to invalid call sequences (e.g. release, prepareAsync) because the reference could change (e.g. due to releasing or opening new video) while the thread was doing things. The thread now always works on the same reference, detects if the reference is outdated and released the (old) player in such a case. This probably fixes GitHub issue #70.
I could not reproduce this, but the issue is probably fixed in Btw, calling if (mVideoView.isPlaying()) {
mVideoView.stopPlayback();
mVideoView.setVideoSource(null);
} in |
I think I added it when trying to debug that weird dash freezing crash you fixed in the last patch. I was testing to see if it had something to do with incomplete teardown when leaving the activity but I never ended up removing it after you fixed the issue. I'll remove it in my next build, thanks for the heads up. Also I'm closing this issue until I see proof that it still exists in 4.3.2 |
I haven't been able to reproduce this yet but I wanted to let you know there's an uncommon crash floating around in there. From the Play Store console the stacktrace looks like this:
Affected devices so far:
Currently used lib version are:
From the source it looks like this is what's triggering the exception:
Any suggestions how to reproduce this?
The text was updated successfully, but these errors were encountered: