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

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


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

health-plan-clankium-phone

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

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Adrienne Walker
  Commit : d82c4fabc5cc6cbe6b475186ed9fa0216980e533
  Date   : Fri Jun 29 22:55:43 2018
  Subject: Turn on OOP Raster on android bots

Bisect Details
  Configuration: clankium-phone-perf-bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:private_dirty_size_avg/background/after_http_www_amazon_com_gp_aw_s_k_nexus
  Change       : 15.08% | 54343768.0 -> 62539864.0

Revision                                       Result                  N
android-chrome@e1215825f7                      54343768 +- 180461      6      good
android-chrome@23ce5c27b6                      54261165 +- 496726      6      good
android-chrome@23ce5c27b6,chromium@571692      54097325 +- 366254      6      good
android-chrome@23ce5c27b6,chromium@571693      54203821 +- 298830      6      good
android-chrome@23ce5c27b6,chromium@571694      62452483 +- 279699      6      bad       <--
android-chrome@23ce5c27b6,chromium@571698      62496173 +- 452221      6      bad
android-chrome@24cae43d5e                      62545325 +- 165154      6      bad
android-chrome@cd28519e8e                      62539864 +- 313891      6      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.www.amazon.com.gp.aw.s.k.nexus 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/8941945437723819632


For feedback, file a bug with component Speed>Bisection