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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgxNrb4QsM


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

android-nexus6

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

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

Suspected Commit
  Author : caitp
  Commit : 0423341034c767d91128c9fd68e3f51e60359c1c
  Date   : Fri Feb 24 17:48:49 2017
  Subject: [async-iteration] implement Async-from-Sync Iterator

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_news/load_news_qq
  Change       : 2.03% | 3247790.66667 -> 3313870.0

Revision                           Result                  N
chromium@452905                    3247791 +- 28924.5      6      good
chromium@452937                    3241876 +- 956.092      6      good
chromium@452953                    3242519 +- 1866.62      6      good
chromium@452957                    3243420 +- 7515.55      6      good
chromium@452958                    3242199 +- 555.976      6      good
chromium@452958,v8@0ba513f056      3242618 +- 2144.22      6      good
chromium@452958,v8@8cfe45b6f1      3243816 +- 29537.2      6      good
chromium@452958,v8@0423341034      3318999 +- 26771.5      6      bad       <--
chromium@452959                    3314248 +- 997.212      6      bad
chromium@452961                    3314276 +- 891.148      6      bad
chromium@452968                    3314369 +- 1012.92      6      bad
chromium@453030                    3313870 +- 1017.27      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.news.qq system_health.memory_mobile

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

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


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