Increase in complexity in the render stream leaks into capture metrics in webrtc_perf_tests |
||
Issue descriptionVersion: 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.
,
Apr 29 2016
This should be filed in the WebRTC tracker, not Chromium. [Changed my comment due to spelling errors.]
,
Apr 29 2016
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 |
||
Comment 1 Deleted