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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgkOCK4AgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg4OiG7ggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg4K715AgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgkOzdoAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg4JfarwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgoNue6gkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgkOzJvgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg4OGG9goM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg4NKe8gkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg4IXl5QoM


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

android-nexus5
android-nexus7v2
android-nexus9

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: android_nexus9_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/browse_news/browse_news_reddit
  Change       : 10.79% | 21189115.4286 -> 23475275.5556

Suspected Commit Range
  2 commits in range
  https://chromium.googlesource.com/chromium/src/+log/b20f0039e91883b8f001390a2f21616b4ec5752d..91a065822077d6e8b89e39d0487896deccaf1bb9


Revision             Result                   N
chromium@444017      21189115 +- 6430079      14       good
chromium@444044      21386510 +- 8298463      14       good
chromium@444050      21098649 +- 6587926      14       good
chromium@444051      ---                      ---      build failure
chromium@444052      23826367 +- 4744977      6        bad
chromium@444053      23859508 +- 6625412      9        bad
chromium@444054      24066133 +- 8016524      14       bad
chromium@444057      23758819 +- 8365712      14       bad
chromium@444070      23475276 +- 7164813      9        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=browse.news.reddit system_health.memory_mobile

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

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


| 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 Tests>AutoBisect.  Thank you!

All related the revert in  Issue 671156 #c52, the regression was expected.