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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDght2foAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghui4iQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghsmhqwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghqmnuQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-rfwvAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-p-K4AoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghqmOoAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-rv4-QoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-v3KqAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgut_V6AgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghqDCvQoM


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

android-nexus5
android-nexus5X
android-nexus7v2

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

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : media.android.tough_video_cases
  Metric       : cpu_utilization/crowd.ogg_browser


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 media.android.tough_video_cases

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

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


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

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

=== Auto-CCing suspected CL author fsamuel@chromium.org ===

Hi fsamuel@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


=== 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_nexus5_perf_bisect
  Benchmark    : media.android.tough_video_cases
  Metric       : cpu_utilization/crowd.ogg_browser
  Change       : 33.39% | 5.3313577114 -> 7.1113718375

Revision             Result                   N
chromium@474467      5.33136 +- 0.277427      6      good
chromium@474522      5.42227 +- 0.322084      6      good
chromium@474536      5.50186 +- 0.127074      6      good
chromium@474538      5.45027 +- 0.569114      6      good
chromium@474539      7.09821 +- 0.168647      6      bad       <--
chromium@474540      6.97635 +- 0.240476      6      bad
chromium@474543      7.03664 +- 0.327365      6      bad
chromium@474550      7.08721 +- 0.222568      6      bad
chromium@474577      7.11137 +- 0.347611      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 media.android.tough_video_cases

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

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


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