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

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


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

perf-go-phone-1024

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: go-phone-1024-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:private_footprint_size_avg/browse_news/browse_news_cricbuzz
  Change       : 0.28% | 50011379.8095 -> 50151424.0

Revision                       Result                   N
android-chrome@dda312c828      50011380 +- 1546243      21      good
android-chrome@0ddfe47bde      50151424 +- 1868337      21      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.cricbuzz 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/8945186356109752880


For feedback, file a bug with component Speed>Bisection