Skip to content
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.

Sign up for GitHub

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

Jump to bottom

HLS Livestream crash and device reboot on Nexus 10 #2806

Closed
starchey opened this issue May 10, 2017 · 2 comments
Closed

HLS Livestream crash and device reboot on Nexus 10 #2806

starchey opened this issue May 10, 2017 · 2 comments
Assignees
@ojw28
Labels
bug: device specific

Comments

@starchey
Copy link

starchey commented May 10, 2017 •
edited
Loading

Issue description

Playing the following HLS livestream, {sent in email}, on a Nexus 10 running 5.1.1 will cause the app to crash and the device to reboot. This is happening 100% on this device, but is not affecting any other Android phones or tablets we have tested. We also notice it only happens when the higher resolution video track is selected, as if we force it to play the lowest, the crash does not occur.

Reproduction steps

  1. Modify ExoPlayer demo app to play live stream mentioned above (have been modifying a URI in media.exolist.json)
  2. Play the stream
  3. Stream will start at lowest resolution track, 400x224, then switch to highest, 1280x720

Within five minutes (typically within one minute), the app will crash and the device will reboot.

Link to test content

Livestream URL sent in email.

Version of ExoPlayer being used

Have tested with ExoPlayer 2.4.0 and latest from dev-v2 branch as of 05/10/17 12:32 MDT. Issue happens in both.

Device(s) and version(s) of Android being used

Nexus 10 Tablet running 5.1.1
This is the only device we have been able to reproduce on, and we can reproduce 100% on this device

A full bug report captured from the device

Bug report available here: https://www.dropbox.com/s/upflxydm5fejoxs/bugreport.txt?dl=0
@ojw28
Copy link
Contributor

ojw28 commented May 25, 2017

I'm able to reproduce this. Whilst it's almost certainly a device issue, we'll take a look and see if there's anything we can do to work around it.

@ojw28 ojw28 self-assigned this May 25, 2017
ojw28 added a commit that referenced this issue May 31, 2017
@ojw28
Move adaptation disabling workaround into MediaCodecUtil
ea21af2 
This is necessary to make sure that the correct thing happens
where MediaCodecInfo.adaptive is queried directly (for example,
MediaCodecVideoRenderer uses the field to determine how to size
input buffers). Also disable adaptive on Nexus 10.

Issue: #2806

-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=157583473
@ojw28
Copy link
Contributor

ojw28 commented May 31, 2017

I think the workaround ref'd above fixes this issue.

@ojw28 ojw28 closed this as completed May 31, 2017
ojw28 added a commit that referenced this issue Jun 6, 2017
@ojw28
Move adaptation disabling workaround into MediaCodecUtil
c36793a 
This is necessary to make sure that the correct thing happens
where MediaCodecInfo.adaptive is queried directly (for example,
MediaCodecVideoRenderer uses the field to determine how to size
input buffers). Also disable adaptive on Nexus 10.

Issue: #2806

-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=157583473
@google google locked and limited conversation to collaborators Sep 29, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@ojw28 ojw28

Labels
bug: device specific
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@starchey @ojw28