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

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


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

health-plan-clankium-low-end-phone

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

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

Bisect Details
  Configuration: clankium-low-end-phone-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:private_dirty_size_avg/browse_chrome/browse_chrome_newtab
  Change       : 1.95% | 32802600.381 -> 32161868.9524

Revision                       Result                   N
android-chrome@dc34638b2d      32802600 +- 2613716      21      good
android-chrome@7d7a6acb1b      32161869 +- 2973235      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.chrome.newtab 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/8946994157101171088


For feedback, file a bug with component Speed>Bisection