Issue metadata
Sign in to add a comment
|
WebRTC video locks up when attaching remote media tracks
Reported by
mbl...@phzio.com,
Oct 23 2017
|
||||||||||||||||||||||
Issue descriptionSteps to reproduce the problem: 1. On a 7.0 Android device in Chrome, launch this example: https://webrtc.github.io/samples/src/content/peerconnection/multiple/ 2. press "Start" 3. Local video starts flowing in first container 4. Press "Call" 5. Local video freezes and remote video never starts flowing. Works on Android 5.0.2 (tested) on same Chrome version. What is the expected behavior? As it works on Chrome desktop and Android 5.0.2. The local feed should continue working and the remote feeds should populate and stream the same video. Peers are in closed loop. What went wrong? It seems triggered by a call to <video>.srcObject = stream when attaching the stream to the video tag. Did this work before? Yes Only tried on 5.0.2 for sure... Chrome version: 61.0.3163.98 Channel: stable OS Version: 7.0 Flash Version: Using a Samsung S8 device. Brand new. I received a crash report from Chrome while testing today that I passed on. It doesn't always crash Chrome though.
,
Oct 23 2017
I tried this page too and on another S8 device, still failing: https://webrtc.github.io/samples/src/content/peerconnection/pc1/
,
Oct 24 2017
Tested the issue using #61.0.3163.98 on Android 6.0.1; SM-G930F Build/MMB29K and could not reproduce the issue as per the steps mentioned below. Steps Followed: 1. Launched Browser 2. Navigated to https://webrtc.github.io/samples/src/content/peerconnection/multiple/ 2. Clicked on "Start", "Call" 4. No Freezing observed on local video and remote video gets started in few seconds. Requesting MTV team to check the issue on Samsung S8 device with 7.0 as it's not available with Clank-Hyd Team. Thanks!!
,
Oct 24 2017
I recorded a video to show the issue: https://photos.app.goo.gl/iTFprvByF6YLbWNT2 Note also that it often happens when I load a page that I get a NotReadableError on the gUM call. The page again for the test is this one: https://webrtc.github.io/samples/src/content/peerconnection/pc1/
,
Oct 26 2017
I can reproduce on an SM-G950F running Android 7.0 and Chrome 61.0.3163.98. The issue does not reproduce on Beta 62.0.3202.52, Dev 63.0.3239.17 or Canary 64.0.3249.0.
,
Oct 26 2017
When is 3202 due for release?
,
Oct 26 2017
Can also reproduce on OnePlus 3 with Android 7.1.1 and Chrome Stable 61.0.3163.98. Does not reproduce on Beta 62.0.3202.52 on the same phone.
,
Oct 26 2017
According to https://omahaproxy.appspot.com/ 62.0.3202.73 is already stable. I guess it's being rolled out.
,
Oct 26 2017
Note also that this did not reproduce on 61 with several other devices I tried. I could only reproduce on the S8 and OnePlus 3 on 61.
,
Oct 27 2017
Removing from the triaging bucket as its already been addressed.( comment #5,7)
,
Oct 31 2017
Just tested with stable 62.0.3202.73 and the issue no longer reproduces on the One Plus 3. Closing as Fixed. Please reopen if you experience the issue again with 62 or newer. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by dglazkov@chromium.org
, Oct 23 2017