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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6M6FpQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6I7t7gkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6ICWtgsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6I7t7goM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgmNitugsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgqKOa4wgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6LWUvwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6IiayAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6KrhsAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6MbG7wsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgqL_HuAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgqP7t9AsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgqJmr-wsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6KaujQgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgqLeljgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6Jy-tAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6JbSsAkM


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/8988181867661049216

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

Suspected Commit
  Author : ssid
  Commit : efed310cc305f0d89f9d1aa49fb5e0d4ec9ff2cd
  Date   : Tue Feb 07 05:29:58 2017
  Subject: [memory-infra] Make client discardable segments non-weak

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : memory.top_10_mobile_stress
  Metric       : memory:chrome:all_processes:reported_by_chrome:skia:effective_size_avg/foreground/http_www_amazon_com_gp_aw_s_k_nexus
  Change       : 167.13% | 76008.0 -> 203038.666667

Revision             Result                  N
chromium@448524      76008.0 +- 0.0          6      good
chromium@448547      76062.7 +- 299.422      6      good
chromium@448553      76008.0 +- 0.0          6      good
chromium@448554      202984 +- 0.0           6      bad       <--
chromium@448555      202984 +- 0.0           6      bad
chromium@448556      202984 +- 0.0           6      bad
chromium@448558      202984 +- 0.0           6      bad
chromium@448569      203039 +- 299.422       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_stress

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

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


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