-
Notifications
You must be signed in to change notification settings - Fork 380
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
Random internal error #642
Comments
When you see this error is it after you have swiped a few pages in the |
It sometimes happens on the very first fragment and sometimes after I have scrolled a lot of fragments. I have made sure to release the VideoView instance (by calling the stopPlayback and release methods) in the onDestroy of the fragment. With a breakpoint I can assure that it is called. I also set offscreen pages limit to 1 so at most 3 instances of the VideoView coexist. I use FragmentStatePagerAdapter for the pagers adapter and I don't hold any instances of the fragments in a list. The strangest fact is that most often it occurs to the first video. |
OK, I'll see if I can track this down. Thanks for the details |
I also face this problem, most same as @tsoumalis said . I uesed Exoplayer in ViewPager, but not in fragment, but in view.
|
Historically we had the We are facing exactly the same issue if workaround is enabled. If you will override this method and return |
Include the following:
4.2.2
8.0
Huawei
Mate 10 Lite
Reproduction Steps
I have a ViewPager where I load a video for each page. Each page is a fragment with a full screen video (I use TextureView to have the video cropped and cover the whole screen). The video either comes from an online URL or from cache. Sometimes, especially when the video originates from cache, I get an error playing the video with the following stack trace:
Expected Result
I would expect the video to play normally.
Actual Result
I mostly get the error with 720p videos. Perhaps it is an internal codec error or internal ExoPlayer error but if I use the stock VideoView I don't have any problems. A strange fact is that before I get the update to Android 8 for this device I didn't face this problem. This only occurs frequently after the update.
I tried to workaround this by using the onError callback and trying 3 times to reset the player in 1 second intervals but I get an error Failed to connect to surface 0x7d2414e010, err -22 which indicates that the surface is already connected to another instance.
The text was updated successfully, but these errors were encountered: