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

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


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

android-nexus5
android-nexus5X
android-one

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

=== 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_one_perf_bisect
  Benchmark    : thread_times.key_silk_cases
  Metric       : thread_GPU_cpu_time_per_frame/font_wipe.html
  Change       : 7.38% | 4.24309949344 -> 4.55612403926

Revision             Result                    N
chromium@517734      4.2431 +- 0.311449        6      good
chromium@517737      4.28403 +- 0.0895962      7      good
chromium@517739      4.30432 +- 0.0745019      6      good
chromium@517740      4.56206 +- 0.0899679      5      bad       <--
chromium@517746      4.55612 +- 0.0762207      5      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=font.wipe.html thread_times.key_silk_cases

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

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


For feedback, file a bug with component Speed>Bisection