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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-vWopgsM


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

android-nexus6

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

=== 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_nexus6_perf_bisect
  Benchmark    : thread_times.key_idle_power_cases
  Metric       : tasks_per_second_total_all/blank.html
  Change       : 733.93% | 7.84155584123 -> 65.3930367826

Revision             Result                   N
chromium@474507      7.84156 +- 6.78874       6      good
chromium@474526      8.97312 +- 7.08436       6      good
chromium@474535      5.99291 +- 0.264863      6      good
chromium@474538      6.89324 +- 5.70085       6      good
chromium@474539      65.5246 +- 0.661523      6      bad       <--
chromium@474540      67.412 +- 6.47226        6      bad
chromium@474544      66.5178 +- 5.71441       6      bad
chromium@474580      65.393 +- 0.617285       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=blank.html thread_times.key_idle_power_cases

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

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


| 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!