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

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


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

health-plan-clankium-phone

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

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

Bisect Details
  Configuration: clankium-phone-perf-bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/background/after_https_www_google_co_uk_hl_en_q_science
  Change       : 0.03% | 38542117.9048 -> 38553186.8571

Revision                       Result                  N
android-chrome@70713a2e5e      38542118 +- 289115      21      good
android-chrome@be902aa047      38553187 +- 242664      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/8946448053565606048


For feedback, file a bug with component Speed>Bisection

Downgrading P2 issues unmodified for more than 6 months, which have no owner or component.