All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=892844

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=2d45394b779563d96cfcda35d63477491e60458283494d4eef53cd949281a18e


Bot(s) for this bug's original alert(s):

mac-10_13_laptop_high_end-perf

media.desktop - Benchmark documentation link:
  None

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/14289c6ae40000

📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/14289c6ae40000

Printing duplex mode restriction policy by vkuzkokov@chromium.org
https://chromium.googlesource.com/chromium/src/+/1afb0f62d66ff0098e0f063364cba42b7fcf972b
time_to_audio_play: 193.6 → 334 (+140.4)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Benchmark documentation link:
  None

WebRTC change seems more likely culprit:
https://webrtc.googlesource.com/src/+/cbcbc225687faf8226995c2823380adf06bd1afb

Hmm, it seems  bug 892845 , not this one, is the one linked to the alert.

If changes are specific to webm, it seems unlikely to be my webrtc cl. Hwo can I reproduce this locally? 

#5 https://chromium.googlesource.com/chromium/src/+/master/docs/speed/addressing_performance_regressions.md#debugging-regressions

I'm sorry I haven't been able to investigate this. I also note that the bug linked to the alert, https://bugs.chromium.org/p/chromium/issues/detail?id=892845, is a closed as won't fix. 

Vladislav, can you decide next step, and maybe close as a dup?