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

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


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

android-webview-nexus5X

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/16cae1f7840000

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/1595815c440000

 Issue 814150  has been merged into this issue.

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/14e468e1440000

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/1595815c440000

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/17c6b57f440000

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/14e468e1440000

📍 Found significant differences after each of 2 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/17c6b57f440000

[fuzzer] Handle more than 256 parameters of the same type by ahaas@chromium.org
https://chromium.googlesource.com/v8/v8/+/bb253d28f48b6a2895b13f8a49d78fcc1be79779

Make histogram CountKiB reusable.  Add CountKilo, too. by bcwhite@chromium.org
https://chromium.googlesource.com/chromium/src/+/2224547f3d96beb34ddd60481b9d260d29c8ed67

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

My CL only moved a piece of code to make it reusable.  It didn't add any new calls or change any execution so shouldn't change performance in any way.  Assigning to 2nd CL.

My CL does not touch production code, only a fuzzer which tests a feature which is off by default.

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/1188d553c40000

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/1188d553c40000

'DiagnosticRef' object is not iterable

Can't bisect due to build failures, and this is mostly in the noise.