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

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


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

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

Bisect Details
  Configuration: clankium-low-end-phone-perf-bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/foreground/https_www_google_co_uk_hl_en_q_science
  Change       : 0.76% | 23934419.0476 -> 24116349.7143

Revision                       Result                  N
android-chrome@a8d6449870      23934419 +- 302114      21      good
android-chrome@3fea53a776      24116350 +- 308822      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=https.www.google.co.uk.hl.en.q.science memory.top_10_mobile

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

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


For feedback, file a bug with component Speed>Bisection

This regression has been open for half a year. It's not very actionable and the regression has been in all Chrome user's hands for months.