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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghq7CrQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-ruprAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghtitqQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-sDKqwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-tWCoAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-rrPtQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-sDKqwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-rrqsQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-sPXuAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-r-k5ggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-tvV4AoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-pyPvwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghpywoQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-vybqAkM


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

android-nexus6
android-one

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

=== 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    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:java_heap:proportional_resident_size_avg/foreground/http_yandex_ru_touchsearch_text_science
  Change       : 11.54% | 14150656.0 -> 15783936.0

Revision             Result                  N
chromium@474507      14150656 +- 459807      6      good
chromium@474537      14125056 +- 398708      6      good
chromium@474538      14152021 +- 433883      6      good
chromium@474539      15814656 +- 489322      6      bad       <--
chromium@474540      15799637 +- 353331      6      bad
chromium@474543      15816533 +- 396901      6      bad
chromium@474548      15852373 +- 519929      6      bad
chromium@474559      15788715 +- 398218      6      bad
chromium@474580      15783936 +- 455748      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 memory.top_10_mobile

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

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


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