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

Issue 607242 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Apr 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Increase in complexity in the render stream leaks into capture metrics in webrtc_perf_tests

Project Member Reported by aluebs@chromium.org, Apr 27 2016

Issue description

Version: ToT
OS: I have seen it on mac bots and repro on my Linux box, so I think it is OS agnostic

What steps will reproduce the problem?
(1) Add some complexity to the render stream in ProcessReverseStreamLocked
(2) compile and run:
./out/Release/webrtc_perf_tests --gtest_filter=AudioProcessingPerformanceTest/CallSimulator.ApiCallDurationTest/* | grep '_capture='
(3) Compare the numbers with and without the additional complexity

What is the expected output?
They should not change.

What do you see instead?
They increase.

Please use labels and text to provide additional information.

 

Comment 1 Deleted

This should be filed in the WebRTC tracker, not Chromium. [Changed my comment due to spelling errors.]

Comment 3 by aluebs@chromium.org, Apr 29 2016

Status: WontFix (was: Assigned)
Makes sense, sorry about that. I just assume here was the place to file it, since we use this tracker for the WebRTC performance issues. I am closing this bug now in favor of: https://bugs.chromium.org/p/webrtc/issues/detail?id=5846

Sign in to add a comment