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

Issue 827211 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

Enabling WebRtcUseGpuMemoryBufferVideoFrame introduced flakiness

Project Member Reported by emir...@chromium.org, Mar 29 2018

Issue description

https://chromium-review.googlesource.com/c/chromium/src/+/963642#message-a3cf8853be5d1e633efa8902b0e9c579ac857dc7

We can see from automated results that it introduced flakiness in WebRtcGetUserMediaBrowserTest.ApplyConstraintsNonDevice, WebRtcGetUserMediaBrowserTest.SrcObjectRemoveFirstOfTwoVideoTracks and WebRtcGetUserMediaBrowserTest.ApplyConstraintsNonDevice tests. We should try to fix these tests, or revert if problems aren't solved.
 
Project Member

Comment 1 by bugdroid1@chromium.org, Mar 30 2018

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

commit d6a295fe18af5a4e181c2b8e1142debf130779a4
Author: Emircan Uysaler <emircan@chromium.org>
Date: Fri Mar 30 15:41:41 2018

Change events for detecting video size for media streams

onprogress is not a reliable event for detecting video size, because when there
is an asynchronous element in pipeline it gets called before video actually
plays. We should use onloadedmetadata instead to avoid flakiness.

Bug:  827211 
Change-Id: I756c05756c37d4dd54926c3b967ae47eef9ae264
Reviewed-on: https://chromium-review.googlesource.com/986988
Reviewed-by: Guido Urdaneta <guidou@chromium.org>
Commit-Queue: Emircan Uysaler <emircan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#547168}
[modify] https://crrev.com/d6a295fe18af5a4e181c2b8e1142debf130779a4/content/test/data/media/getusermedia.html

Status: Fixed (was: Started)

Sign in to add a comment