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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg__bR5QsM


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

chromium-webrtc-rel-linux

This is a very strange bug.
The only CL in the blame list is a reland, which doesn't make sense, since neither the original CL, nor the revert seemed to have any effect on the performance metrics.

https://chromium.googlesource.com/external/webrtc/trunk/webrtc/+/5445b0716f1a96eb11cc3745093c058dffd53227

The Chromium revisions in the blame list are: https://chromium.googlesource.com/chromium/src/+log/b520619b133f1b3609461153afd0ffb81bfd5bdc%5E..a576f652af13438c3867a306ce847e87585dcb7b

I suspect mcasas@'s https://chromium.googlesource.com/chromium/src/+/50252de90c71b7d5d12c30121a82d4e790f74252 may be the culprit.

Hmmm, I now noticed that the revision ranges are not entirely overlapping but that's probably just one alert that needs to be nudged. I'll leave it to the triager to investigate further.

Ranges are pointing to 442081 as well here, dup of  issue 681832 .

https://chromium.googlesource.com/chromium/src/+/50252de90c71b7d5d12c30121a82d4e790f74252