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

Issue 841164 link

Starred by 1 user
Status: WontFix
Owner:
m...@chromium.org
Closed: May 2018
Cc:
niklase@chromium.org
█ sandeepkumars@chromium.org
█ phoglund@chromium.org
rantonysamy@chromium.org
jansson@chromium.org
mflodman@chromium.org
mfo...@chromium.org
sprang@chromium.org
brandtr@chromium.org
terelius@chromium.org
powerb@chromium.org
holmer@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Video feed jitters upon screen sharing from Linux machine [All webrtc apps are affected]

Project Member Reported by vasanthakumar@chromium.org, May 9 2018 
Chrome Version: 66.0.3359.139 [Live stable build]
OS: Linux Z440 

System configuration: Debian rodete x86-64, Cinnomon version 3.4.6, Intel Xeon CPU E5-1650 V3 @ 3.50 GHz x 6, Memory 31.4GB, Graphics card GM107GL (Quadro K620)

What steps will reproduce the problem?
(1) Open any webrtc live apps like Hangouts, Meet, Appear.in etc
(2) Perform a webrtc call and start screen sharing
(3) Choose "Your entire screen" and observe if the preview is fine
Tip: Make sure camera captures some movement

What is the expected result?
Screen share preview and screen share is free from jitters. 

What happens instead?
Screen share preview window jitters as shown in the video. Even after sharing we can observe similar jitters. This is bad experience to the user and it will be nice to get fixed. 

Regression?
It needs to be verified if this issue is reproducible in M65 and M64. Soon I can bisect and update here in the bug. 

Potential Reason?
Decoding the video seems to play a role here. 

Note:
When the screen share is done for a particular window this issue is not reproducible. For example tried few times of sharing the terminal window. It worked fine. Thus stressing the decoder/encoder could play a role for this behavior. 

As of now reproducible in all later versions like M67 / 67.0.3396.30 and M68 / 68.0.3423.2.
gpu.html
71.2 KB View Download
Video 1.mp4
5.1 MB View Download
Video 2.mp4
2.0 MB View Download
event_log_20180509_1006_12_1.log
1.0 MB View Download
webrtc_internals_dump.txt
108 KB View Download

Comment 1 by vasanthakumar@chromium.org, May 9 2018 

External cameras used for this test are as follows. 
Logitech Webcam C930e
Logitech Brio 4K Stream Edition (046d:086b)

Reproducible in both the cameras.

Comment 2 by yini...@chromium.org, May 9 2018

Owner: m...@chromium.org
Status: Assigned (was: Untriaged)

Comment 3 by krajshree@chromium.org, May 10 2018

Labels: TE-NeedsTriageFromHYD Triaged-ET Needs-Triage-M66
Tried testing the issue on ubuntu 17.10 using chrome version #66.0.3359.139 as per comment #0.
Observed that on Choosing "Your entire screen" while screen sharing the window was shown as black screen and did not show any image of the entire screen.
From comment #0, the issue seems to be reproducible on Debian rodete x86-64, Cinnomon version 3.4.6, Intel Xeon CPU E5-1650 V3 @ 3.50 GHz x 6, Memory 31.4GB, Graphics card GM107GL (Quadro K620) and using external camera. As ET-team doesn't have any external camera to test the issue.
Hence, forwarding the issue to inhouse team for further triaging the issue.

Thanks...!!

Comment 4 by vasanthakumar@chromium.org, May 11 2018 

This issue is reproduced in 66.0.3359.139, 65.0.3325.51, 64.0.3282.204, 60.0.3112.98.

Thus it can be older bug.

Comment 5 by sandeepkumars@chromium.org, May 11 2018

Cc: sandeepkumars@chromium.org
Labels: -Needs-Bisect -TE-NeedsTriageFromHYD
Thanks @vasanthakumar for confirmation, removing the needs-bisect as per C#4 as this is non regression issue seen from M-60.

Thanks!!

Comment 6 by sprang@chromium.org, May 11 2018 

Think this was reported earlier and determined to be an OS bug and not chrome issue.

b/67487551

Comment 7 by vasanthakumar@chromium.org, May 11 2018

Status: WontFix (was: Assigned)
Thank you Sprang. I just gone through the bug and realized that's duped into b/70981219. Thus I will close this ticket for now. 

If needed in future we can re-open it again.
►

Sign in to add a comment