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

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


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

android-nexus5x-perf

blink_perf.dom - Benchmark documentation link:
  https://bit.ly/blink-perf-benchmarks

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/11aab8e3640000

📍 Found significant differences after each of 3 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/11aab8e3640000

Include testing of significant impacts on a per story basis. by anthonyalridge@google.com
https://chromium.googlesource.com/catapult/+/313f37ed7bc8369d51dbc1d5cb4afcbd48aa5dbb
14.14 → 13.79 (-0.35)

Roll src/third_party/catapult 713e916190aa..88dc49aaadb0 (3 commits) by catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com
https://chromium.googlesource.com/chromium/src/+/fcfe9a6f17f02771890c03d666dcebf560eca909
13.79 → 20 (+6.21)

Remove unused MockFrameDropper and make FrameDropper non-virtual. by brandtr@webrtc.org
https://webrtc.googlesource.com/src/+/260182d9f3042f1bd4534271c95d77cc1a43556f
19.96 → 19.07 (-0.895)

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

Benchmark documentation link:
  https://bit.ly/blink-perf-benchmarks

Assign to pasko@ based on bisecting in #c2, 

There are three commits causing performance regression:
2018-09-03 pasko@chromium.org devil: Limit CPU/GPU frequency for Nexus 5X
2018-09-03 anthonyalridge@google.com Include testing of significant impacts on a per story basis.
2018-09-03 wangge@google.com Add M70 branch number.