Attaching screenshot for reference.

Deleted: Actual_Blank Video.png 134 KB

	Actual_Blank Video.png 134 KB View Download

Able to reproduce the issue on chrome 53.0.2768.0/8459.0.0 (Blaze) as per the steps mentioned in the above comment. No video is displayed while having a hangout out call instead a black screen is seen.

This issue is not seen in #52.0.2743.11/8350.13.0_Dev Blaze. Hence adding Dev blocker label as it is recent regression issue.

Note:1.This issue is not seen when we join hangouts call using devices Jerry,Peppy,Daisy with Version: 53.0.2768.0/8459.0.0 (Official Build) dev

So, the Hangout session is between a nyan_blaze device on one side 1) and another device on the other side 2), and the issue is observed on side 2), right?

What were the devices on side 2), failing in #0?

In #2, was nyan_blaze on both sides? Was the issue observed on both sides?

Can you generate logs, and link them here.

Ranjani, could you check if apprtc is working?

 Issue 612198  ?

Yes. This This issue appears similar to https://bugs.chromium.org/p/chromium/issues/detail?id=612198 which was filed on M51 beta version and was also seen on M52 beta for device Blaze.

rohitbm@:

I have tested AppRTC calls and hangouts on device Blaze with M53 53.0.2768.0 / 8459.0. dev

- AppRTC calls with default video codec VP9 is working fine 
- Remote video is freezing on AppRTC loopback, Peer2peer with sending video codec VP8 
- Remote video is freezing as soon as the hangout call starts
- Filed https://bugs.chromium.org/p/chromium/issues/detail?id=620848 for this issue

Note: Hangouts were tested between device Blaze with M53 dev and Linux desktop with M51 stable

Any ideas as to the timeline for resolving this?

With this being a dev blocker we are holding back deployment of a dev image with a critical touch pad fix. 

The touchpad issue is on Blaze so perhaps we could block the other Nyan systems, but ship Blaze with a Dev with this regression to get the touchpad issue moving?

Hangouts is a very important use-case so I would say we should skip Nyan-* device until this issue is fixed.

I experienced the same issue today with the Asus Flip in a Hangout with 6 other people on different chromebooks.

Version 52.0.2743.32 dev
Platform 8350.21.1 (Official Build) dev-channel veyron_minnie
Firmware Google_Veyron_Minnie.6588.171.0

I host the weekly video Hangout at 2pm EDT > started fine > after a couple of minutes > black screen but could see the people at the bottom of screen. 

Ended Hangout > repeated the issue > switched to Acer 15 > no problems

Version 51.0.2704.79 (64-bit)
Platform 8172.47.0 (Official Build) stable-channel auron_yuna
Firmware Google_Auron_yuna.6301.59.8

I did not send feedback at the time but did send one now at 7:19pm EDT
"Black screen feedback for  Issue 620676 "

Ranjani, could you file a different problem for the Minnie issue?

This is likely a duplicate of  issue 612198 . We are waiting for the PFQ to pick up the fix in Chrome.

https://codereview.chromium.org/2071953003 is in review. With the fix of 612198 and this patch, this issue should be fixed.

Sent https://codereview.chromium.org/2071953003 to CQ.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/95f4096226a6def5622a4d51634acb5e5b808451

commit 95f4096226a6def5622a4d51634acb5e5b808451
Author: wuchengli <wuchengli@chromium.org>
Date: Fri Jun 17 12:07:55 2016

RtcVideoEncoder: use the current timestamp for encoded frames.

Nyan provides invalid timestamps in frame callback. Change back
to the current time before it is fixed.

BUG= chromium:620676 
TEST=Run apprtc loopback and VEA test on nyan-big and oak.

Review-Url: https://codereview.chromium.org/2071953003
Cr-Commit-Position: refs/heads/master@{#400415}

[modify] https://crrev.com/95f4096226a6def5622a4d51634acb5e5b808451/content/renderer/media/rtc_video_encoder.cc

This will be fixed when chrome uprev.

rohitbm@:

Reg. comment#13, I did not exactly replicate the scenario ( hangout with 6 users on different chrome books) but could not reproduce this issue on device Minnie with M52 (52.0.2743.41 / 8350.31.0) beta during hangout with Linux desktop. Stayed in the hangout call for roughly 10 minutes.

WebRTC internal dump from device Minnie and desktop: 
https://pantheon.corp.google.com/storage/browser/chromiumos-test-logs/bugfiles/cr/620676/

Keep the bug open until chrome uprev.

Fixed in 8481.0.0.

Song, could you verify this bug?

Not reproduce the issue on CrOS 8530.35.0/53.0.2785.36 - Blaze. The hangout works fine between blaze and Parrot/Kip devices. 

bj00129141@ 
Please reopen it if you still see the issue.