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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-qq18woM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghvH_4QgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-qWa9wgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-v33rAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghri3qwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-pH5-AgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-omEqgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-t7nvQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgur_d8woM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgur_d8wgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-ue5vQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghp7mpAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghurypQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-t2QuAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-qnCowkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-vHV_QgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-v-htAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-v-f4wgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghoDHrwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-s2hpwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-qmdugoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghoDHrwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-v-fowsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghs7lqQoM


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

android-nexus6
android-nexus7v2
android-one

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

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

Suspected Commit
  Author : fsamuel
  Commit : b520968f4ac40fb89ce25329134b388ca42cca12
  Date   : Thu May 25 03:10:42 2017
  Subject: cc::SurfaceDependencyTracker should not crash when a Display goes away

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : thread_times.key_idle_power_cases
  Metric       : tasks_per_second_total_all/set-timeout.html (Long Idle)
  Change       : 1905.89% | 3.18424444143 -> 63.8725301364

Revision             Result                    N
chromium@474412      3.18424 +- 0.0259781      6      good
chromium@474478      3.221 +- 0.101606         6      good
chromium@474511      3.20463 +- 0.042429       6      good
chromium@474527      3.20358 +- 0.0650741      6      good
chromium@474535      3.22414 +- 0.126589       6      good
chromium@474537      3.22296 +- 0.0611298      6      good
chromium@474538      3.2161 +- 0.0686663       6      good
chromium@474539      63.8754 +- 0.172665       6      bad       <--
chromium@474543      63.8725 +- 0.241286       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=set.timeout.html..Long.Idle. thread_times.key_idle_power_cases

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8978491893160868256

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5305516743458816


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!