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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-sX2owkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-snQ4QgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghpr1tgsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-qOr8gkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghqzfiwgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghumB_QoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghuamswkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-o_-vQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghpKOvQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghqCJswsM


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

android-nexus5
android-nexus5X
android-nexus6
android-one

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

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

Suspected Commit
  Author : fsamuel
  Commit : d71466ad118aca05aa347c9766f80a5f77528588
  Date   : Thu May 25 20:35:22 2017
  Subject: cc::SurfaceDependencyTracker should not crash when a Display goes away

Bisect Details
  Configuration: android_one_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_m_intl_taobao_com_group_purchase_html
  Change       : 17.17% | 6725461.33333 -> 7880362.66667

Revision             Result                 N
chromium@474738      6725461 +- 118858      6      good
chromium@474768      6669141 +- 126084      6      good
chromium@474776      6616405 +- 225125      6      good
chromium@474780      6630400 +- 103124      6      good
chromium@474782      6636203 +- 229644      6      good
chromium@474783      7886165 +- 169618      6      bad       <--
chromium@474797      7846912 +- 251592      6      bad
chromium@474856      7880363 +- 221628      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/8978194970837184672

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


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