New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 769735 link

Starred by 4 users

Issue metadata

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



Sign in to add a comment

Using WebRTC video call make Chrome mobile freeze

Reported by n.cheva...@gmail.com, Sep 28 2017

Issue description

Steps to reproduce the problem:
1. Launch a webrtc call (using for example appr.tc site) on an Android mobile version 7 (nougat) or 8 (oreo) using Chrome version 61.0.3163.98
2. When the call is established, the mobile UI freeze, the video is stopped but the remote still receive your stream.

What is the expected behavior?
Should not freeze and work like in Chrome 60 mobile (and previous) versions.

What went wrong?
My local video and remote video during Webrtc call are frozen.

Did this work before? Yes 60.x.x.x

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

Seems to have this bug in CHrome 62 (beta) too.
 
Tested on Android 7 (Google pixel phone and Samsung S7) and on Android 8 (Google Pixel)
Same issue than 769622
Components: -Blink Blink>WebRTC
Labels: Needs-Bisect Needs-triage-Mobile

Comment 5 by guidou@chromium.org, Sep 29 2017

Components: -Blink>WebRTC Blink>WebRTC>Video
Cc: msrchandra@chromium.org nyerramilli@chromium.org ligim...@chromium.org sandeepkumars@chromium.org
Labels: -Needs-Bisect hasbisect-per-revision Triaged-Mobile
Owner: liber...@chromium.org
Status: Assigned (was: Unconfirmed)
Able to reproduce the issue using #61.0.3163.98, #63.0.3226.0 in Android 8.0.0 Pixel Build/OPR1 170623.027.

Below is the bisect info
=======================

Chrome Good Build -- 61.0.3142.0
Chrome Bad Build  -- 61.0.3143.0

https://chromium.googlesource.com/chromium/src/+log/61.0.3142.0..61.0.3143.0?pretty=fuller&n=10000

Results from pre revision bisect --
You are looking for a change made after 482822(GOOD), but before 482823(BAD).

From the above revision range suspecting the following --
https://chromium.googlesource.com/chromium/src/+/68ec57f3e3114a39ea147c7fe956fa3b9d3a601d

@liberato -- Could you please look into the issue, kindly re-assign if this is not related to your changes.

Note:
1. Issue is seen in M63 as well.
2. Issue is not seen using #61.0.3163.100, #63.0.3226.0 on Linux Ubuntu 14.04, Mac 10.12.6, Win 10.

Thanks!!

Mergedinto: 769148
Status: Duplicate (was: Assigned)
this no longer repros.  probably a dupe of 769148, which was also merged back to M62.

Sign in to add a comment