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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=3af2501f370e8aaa38e4f1bec8ce938f28a2db00bd163108dfae5e2d8c44116e


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

perf-go-phone-512

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

=== 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: go-phone-512-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/browse_news/browse_news_cnn
  Change       : 20.14% | 7302580.85714 -> 8548057.42857

Suspected Commit Range
  2 commits in range
  https://chromium.googlesource.com/chromium/src/+log/7e6ff974382762039600bb435df68218cb237e57..4a2ebc8dad89ca0042d0babd619f4ea35e3ac072


Revision                                       Result                  N
android-chrome@bfbc254ab1                      7302581 +- 419361       14       good
android-chrome@bfbc254ab1,chromium@568611      7290293 +- 756472       14       good
android-chrome@bfbc254ab1,chromium@568612      7626750 +- 435698       14       good
android-chrome@bfbc254ab1,chromium@568613      ---                     ---      build failure
android-chrome@bfbc254ab1,chromium@568614      8834615 +- 940107       9        bad
android-chrome@bfbc254ab1,chromium@568615      8444487 +- 786234       14       bad
android-chrome@bfbc254ab1,chromium@568623      8386851 +- 875309       14       bad
android-chrome@bfbc254ab1,chromium@568638      8212283 +- 849162       21       bad
android-chrome@bfbc254ab1,chromium@568669      8491006 +- 1379067      14       bad
android-chrome@3447e60a36                      8091548 +- 1046091      21       bad
android-chrome@2112fdecff                      8548057 +- 1047552      14       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-chrome --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.cnn system_health.memory_mobile

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8942756398716662080


For feedback, file a bug with component Speed>Bisection