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

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


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

android-nexus5X

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : thread_times.key_silk_cases
  Metric       : thread_other_cpu_time_per_frame/inbox_app.html?toggle_drawer

Revision             Result                    N
chromium@522333      0.825926 +- 0.341822      21      good
chromium@522390      0.818741 +- 0.239849      21      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=inbox.app.html.toggle.drawer 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/8960318676843627184


For feedback, file a bug with component Speed>Bisection

Just happens on one device/page, and bisect can't repro.