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

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


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

health-plan-clankium-low-end-phone
perf-go-phone-512

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

=== 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/background/after_http_yandex_ru_touchsearch_text_science
  Change       : 0.22% | 17107749.1429 -> 17070446.2857

Revision                       Result                   N
android-chrome@0c10befa36      17107749 +- 85341.4      21      good
android-chrome@0e33d541ac      17070446 +- 82611.7      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.yandex.ru.touchsearch.text.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/8940073964777790880


For feedback, file a bug with component Speed>Bisection

These are noisy charts and the bisect can't reproduce the clearest regression.