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

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


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

android-nexus5x-perf

v8.browsing_mobile - Benchmark documentation link:
  None

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/1271b68d640000

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

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
363.2 → 642.3 (+279.2)

Assigning to sheriff sullivan@chromium.org because "Roll src/third_party/catapult 713e916190aa..88dc49aaadb0 (3 commits)" is a roll.

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

Benchmark documentation link:
  None

Hi Annie, bisect pointed to a catapult roll.

These are all on Nexus 5X, so this is almost certainly due to:

2018-09-03 pasko@chromium.org devil: Limit CPU/GPU frequency for Nexus 5X

Closing as WontFix, but assigning to pasko who can follow up if there are any issues with the CL.