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

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


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

health-plan-clankium-phone

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

=== 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_chrome:malloc:effective_size_avg/background/after_http_m_intl_taobao_com_group_purchase_html
  Change       : 0.82% | 30036790.8571 -> 30284480.2381

Revision                       Result                  N
android-chrome@e1215825f7      30036791 +- 338875      21      good
android-chrome@cd28519e8e      30284480 +- 470180      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=http.m.intl.taobao.com.group.purchase.html 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/8942005521134495408


For feedback, file a bug with component Speed>Bisection

Can't see bots any more.