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

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


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

android-nexus5

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8962045846518297680

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Robert Sesek
  Commit : 6f117f26d776f0ba5657451d89800f556a30c3f3
  Date   : Mon Nov 20 00:56:36 2017
  Subject: Introduce the new CrashKeyString API.

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : thread_times.key_mobile_sites_smooth
  Metric       : thread_GPU_cpu_time_per_frame/http___slashdot.org_
  Change       : 3.21% | 2.80184149051 -> 2.89173407417

Revision             Result                    N
chromium@517737      2.80184 +- 0.0621278      6      good
chromium@517739      2.80197 +- 0.04299        6      good
chromium@517740      2.89216 +- 0.0644887      6      bad       <--
chromium@517741      2.89173 +- 0.0333855      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...slashdot.org. thread_times.key_mobile_sites_smooth

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8962045846518297680


For feedback, file a bug with component Speed>Bisection