New issue
Advanced search Search tips

Issue 666967 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jan 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Remote video freezes for long time (~35 seconds) after initiating screensharing from chrome device Jaq

Project Member Reported by srcv@chromium.org, Nov 18 2016

Issue description

Version: 56.0.2923.0 / 9000.0.0 dev
Chrome device: Jaq

What steps will reproduce the problem?
1. Join a two way successful hangout call between chrome device Jaq and Linux desktop
2. From chrome device Jaq, select the screenshare option from the hangout window
3. A new window with the different screens shows up for the selection
4. Select any one of the options from the mini window and then click on 'Share' option at the bottom

What is the expected result?
Selected screen should be shared and displayed on desktop user screen without much delay

What happens instead?
Remote video freezes for 35 seconds (roughly) before it starts displaying the shared screen on desktop

Feedback submitted for this issue:
https://feedback.corp.google.com/product/208/neutron?lView=rd&lRSort=1&lROrder=2&lRFilter=1&lReportSearch=user:srcv&lReport=16656499617

Notes:
I will check this issue on Jaq with latest M55 beta build for regression and update this bug

 

Comment 1 by srcv@chromium.org, Nov 18 2016

WebRTC internal dump, device logs and hangout logs from device Jaq:
https://pantheon.corp.google.com/storage/browser/chromiumos-test-logs/bugfiles/cr/666967/
Labels: -M-56 M-57

Comment 3 by srcv@chromium.org, Jan 5 2017

Labels: -M-57 M-56
Status: WontFix (was: Untriaged)
Re-tested hangouts on chrome device Jaq with latest M56 beta build 56.0.2924.53 / 9000.50.0 beta

Observed that screensharing starts working only after first few attempts of screensharing or rejoining the existing hangout call (https://bugs.chromium.org/p/chromium/issues/detail?id=647775) and there is not much lag in sharing the selected screen as mentioned in the bug report.

Sign in to add a comment