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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnLX6zQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnPjWlQgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnNDQkQgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7MqQ7AkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7M_n4woM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnJWonQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7MqQvAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7MqQvAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7NPX5AoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnP7gpgsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7MXu_wgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7M_n4wgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7LXv6AoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnLzf6wkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnKbw_AgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnLX6rQgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7IuVrQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg3MSivQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnLD75wkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnK3-4AgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg3MSivQoM


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

android-nexus6
android-nexus7v2
android-webview-nexus5X

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

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

Suspected Commit
  Author : Caitlin Potter
  Commit : bf463c4dc080abb1ae39c6f0a93e6a95867b0ca3
  Date   : Wed Mar 29 17:33:12 2017
  Subject: [async-iteration] implement AsyncGenerator

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/load_games/load_games_lazors
  Change       : 2.85% | 2538705.33333 -> 2610973.33333

Revision                           Result                  N
chromium@460544                    2538705 +- 189.877      6      good
chromium@460584                    2538671 +- 240.178      6      good
chromium@460604                    2538705 +- 189.877      6      good
chromium@460614                    2496984 +- 270610       7      good
chromium@460619                    2538705 +- 189.877      6      good
chromium@460620                    2538705 +- 189.877      6      good
chromium@460620,v8@6234fda3c9      2538735 +- 1137.78      6      good
chromium@460620,v8@bf463c4dc0      2586972 +- 254.747      6      bad       <--
chromium@460620,v8@367d646a9e      2591016 +- 21580.3      6      bad
chromium@460620,v8@5615e5b866      2610805 +- 189.877      6      bad
chromium@460621                    2611008 +- 0.0          6      bad
chromium@460622                    2610973 +- 189.877      6      bad
chromium@460624                    2610973 +- 189.877      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=load.games.lazors system_health.memory_mobile

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

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


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