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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-tzxuAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgur_49QkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-vHwuQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghu7erwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghu7erwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-q7orgsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghsm1ugoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-tyYoQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-pWqmwgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-vHV_QoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghu6qtgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghq77qwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgho6p-wgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-uHN9woM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghsCasQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghs7lqQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghu60pwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-tqiqwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-q68_wkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-t_18woM


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

android-nexus6

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

=== 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    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:java_heap:proportional_resident_size_avg/browse_tools/browse_tools_maps
  Change       : 16.33% | 20508672.0 -> 23858346.6667

Revision             Result                   N
chromium@474507      20508672 +- 144141       5      good
chromium@474526      20696235 +- 723216       6      good
chromium@474535      20646741 +- 707083       6      good
chromium@474537      20669611 +- 247962       6      good
chromium@474538      20662784 +- 408009       6      good
chromium@474539      23696043 +- 855352       6      bad       <--
chromium@474544      23964331 +- 1069165      6      bad
chromium@474580      23858347 +- 678988       6      bad

Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

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=browse.tools.maps system_health.memory_mobile

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

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


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