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

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


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/8947093797853292688

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: clankium-low-end-phone-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/browse_chrome/browse_chrome_newtab


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/8947093797853292688


For feedback, file a bug with component Speed>Bisection

This recovered.