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

Issue 748417 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Aug 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 1
Type: Bug



Sign in to add a comment

Merge WebRTC r18998 and r19018 to M60

Project Member Reported by sprang@chromium.org, Jul 25 2017

Issue description

We've had several reports of video corruptions in webrtc. After some tricky debugging, two separate issues were identified and fixed:

One affecting screensharing:
https://bugs.chromium.org/p/webrtc/issues/detail?id=7980
https://chromium.googlesource.com/external/webrtc/+/f03ea04176fbdad3d2efb88eb3c6d2edae1c3586

Another affecting regular multi-way video:
https://bugs.chromium.org/p/webrtc/issues/detail?id=7768
https://chromium.googlesource.com/external/webrtc/+/9bd1d66995ed9ea4712451bc149a8139775cba3c

Both of these can severely impact the user experience (see screenshot in  bug 7768 ).
Fixes have been in M61 and ToT for almost two weeks, and seem stable an working.

These fixes should be merged also to M60.
 

Comment 1 by sprang@chromium.org, Jul 25 2017

Cc: philipel@chromium.org

Comment 2 by sprang@chromium.org, Jul 25 2017

Summary: Merge WebRTC r18998 and r19018 to M60 (was: Merge WebRTC r18998 and r19018 M60)
Project Member

Comment 3 by sheriffbot@chromium.org, Jul 25 2017

Labels: -Merge-Request-60 Hotlist-Merge-Review Merge-Review-60
This bug requires manual review: Request affecting a post-stable build
Please contact the milestone owner if you have questions.
Owners: amineer@(Android), cmasso@(iOS), josafat@(ChromeOS), bustamante@(Desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 4 by pbos@chromium.org, Jul 27 2017

Cc: pbos@chromium.org
Cc: bustamante@chromium.org
+bustamante@
My recommendation is to wait until M61 since M60 is already in stable ramp-up. This merge will require a respin. Can you please confirm if this is a critical issue or can it wait until M61? The fixes don't seem too large and it appears it's well tested. 
Labels: -Merge-Review-60 Merge-Rejected-60
I'd also like to wait until M61, do you have numbers of on the number users affected?  Rejecting for now, feel free to add the "Merge-Review-60" label back if you think this is critical.

Comment 7 by sprang@chromium.org, Jul 31 2017

Depends on how you define critical I guess, but it definitely makes for a very bad user experience. It manifests in the video feed looking something like this:

https://bugs.chromium.org/p/webrtc/issues/attachment?aid=287587&inline=1

We're estimating that something like 3% of calls are experiencing this, but it will depend a lot on how much packet loss is present (higher packets loss makes it more likely to occur). 
Labels: -Merge-Rejected-60 Merge-Approved-60
3% of video calls meets the bar.  Approving for merge into M60.
Project Member

Comment 9 by bugdroid1@chromium.org, Aug 1 2017

Labels: merge-merged-60
The following revision refers to this bug:
  https://chromium.googlesource.com/external/webrtc.git/+/6294a7eb71c891e9ea41273a7a94113f6802d0da

commit 6294a7eb71c891e9ea41273a7a94113f6802d0da
Author: Erik Språng <sprang@webrtc.org>
Date: Tue Aug 01 09:33:37 2017

Merge WebRTC r18998 and r19018 to M60 branch

This CL is cherry pick of the following two commits:

1) RtpFrameReferenceFinder VP8 reference calculation fix.

Review-Url: https://codereview.webrtc.org/2980943003
Cr-Commit-Position: refs/heads/master@{#19018}

2) Fix potential incorrect sync flags used with screenshare TL stream.

Review-Url: https://codereview.webrtc.org/2978743002
Cr-Commit-Position: refs/heads/master@{#18999}

TEST=webrtc unit tests plus manual verification.
BUG= chromium:748417 ,  webrtc:7768 ,  webrtc:7980 
R=philipel@webrtc.org

Review-Url: https://codereview.webrtc.org/2992123002 .
Cr-Commit-Position: refs/branch-heads/60@{#11}
Cr-Branched-From: c61bf947b4ac31f3500858ffcae6fee39d799930-refs/heads/master@{#18252}

[modify] https://crrev.com/6294a7eb71c891e9ea41273a7a94113f6802d0da/webrtc/modules/video_coding/codecs/vp8/default_temporal_layers.cc
[modify] https://crrev.com/6294a7eb71c891e9ea41273a7a94113f6802d0da/webrtc/modules/video_coding/codecs/vp8/screenshare_layers.cc
[modify] https://crrev.com/6294a7eb71c891e9ea41273a7a94113f6802d0da/webrtc/modules/video_coding/codecs/vp8/screenshare_layers_unittest.cc
[modify] https://crrev.com/6294a7eb71c891e9ea41273a7a94113f6802d0da/webrtc/modules/video_coding/codecs/vp8/temporal_layers.h
[modify] https://crrev.com/6294a7eb71c891e9ea41273a7a94113f6802d0da/webrtc/modules/video_coding/rtp_frame_reference_finder.cc
[modify] https://crrev.com/6294a7eb71c891e9ea41273a7a94113f6802d0da/webrtc/modules/video_coding/rtp_frame_reference_finder_unittest.cc

Project Member

Comment 10 by sheriffbot@chromium.org, Aug 4 2017

Cc: bustamante@google.com
This issue has been approved for a merge. Please merge the fix to any appropriate branches as soon as possible!

If all merges have been completed, please remove any remaining Merge-Approved labels from this issue.

Thanks for your time! To disable nags, add the Disable-Nags label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 11 by pbos@chromium.org, Aug 4 2017

Labels: -Merge-Approved-60

Comment 12 by pbos@chromium.org, Aug 4 2017

Status: Fixed (was: Assigned)

Sign in to add a comment