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

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


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

health-plan-clankium-phone

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to continue

Bisect was stopped because a commit couldn't be classified as either
good or bad.


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       : 1.34% | 29999787.8095 -> 30400581.5714

Revision                       Result                  N
android-chrome@e1215825f7      29999788 +- 355756      21      good
android-chrome@23ce5c27b6      29996215 +- 402299      21      good
android-chrome@24cae43d5e      30325411 +- 308358      21      unknown
android-chrome@cd28519e8e      30400582 +- 358696      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/8942005766141134720


For feedback, file a bug with component Speed>Bisection