New issue
Advanced search Search tips
Starred by 15 users

Issue metadata

Status: Duplicate
Merged: issue 769148
Owner: ----
Closed: Oct 2017
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug-Regression

Sign in to add a comment

Issue 769622: Chrome 61 on Android 6.01 or 7.0 Received Video Freezes

Reported by, Sep 28 2017

Issue description

Steps to reproduce the problem:
1. Set up a WebRTC call between Windows Desktop and Android device with captured/sent video resolution higher than 320x240
2. Observe the Android browser and see that the received video track is either not rendered at all or freezes very soon. 

1. Connect call at low 320x240 resolution and confirm all is OK.
2. Screen share from Desktop at high res low frame rate (1280x720@5fps)
3. Observe Android browser is unresponsive and sharing is not displayed.  

What is the expected behavior?
Standard 640x480 or higher video tracks should decode and render well on recent Android devices. 

What went wrong?
The Android browser becomes unresponsive Chrome error sequence is report on device connected to Android Device Monitor:] Error: 5 for Command kSwapBuffers] Context lost because SwapBuffers failed.]   GLES2DecoderImpl: Trying to make lost context current.

Generally this continues as long as the video track is being received, but in a few tests, it did recover. 

Did this work before? Yes Works on Android 5.1.1 Samsung Tablet with same Chrome Version.

Chrome version: 61.0.3163.98  Channel: stable
OS Version: 7.0
Flash Version: 

Error is reproducible on Android 7.0 and 6.01 on
Galaxy S7/S7 Edge, HTC 10, Pixel, Nexus 5 devices

Comment 1 Deleted

Comment 2 by, Sep 28 2017

Components: Blink>WebRTC

Comment 3 by, Sep 28 2017

Requesting WebRTC team to triage.

Comment 4 by, Sep 29 2017

Also reproducible on Samsung Tab S 10" with Android 6.0.1 and same browser version as above.

Comment 5 by, Sep 29 2017

Components: -Blink>WebRTC Blink>WebRTC>Video

Comment 6 by, Oct 2 2017

Mergedinto: 769148
Status: Duplicate (was: Unconfirmed)

Comment 7 by, Oct 4 2017

Found a workaround: set "border-radius: 0px" css property of the video tag. I think it changes something in the rendering process.

ps: only stops rendering if there is no debugger attached

Comment 8 by, Oct 5 2017

 Issue 771819  has been merged into this issue.

Comment 9 by, Nov 3 2017

I also have it reproduced on a Nexus 6P with Android version 8.0.0 kernel version 3.10.73-gad82c6620de built on Wed Aug 16 15:24:10 UTC.

About Chrome reports:
Application version: 61.0.3163.98
Operating system: Android 8.0.0; Nexus6P Build/OPR5.170623.007

Can confirm border-radius fixes the issue, but only if I set it to 1px in my particular application...

I tried AppRTC, but didn't get the exact same issue. There it was really slow before eventually crashing the page (!)

Comment 10 by, Nov 3 2017's new PWA thing works fine though

Sign in to add a comment