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

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


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

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

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

=== Auto-CCing suspected CL author enne@chromium.org ===

Hi enne@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


=== 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    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/load_media/load_media_imgur
  Change       : 247.25% | 38050562.6667 -> 132130904.0

Revision                                       Result                   N
android-chrome@e1215825f7                      38050563 +- 334670       6      good
android-chrome@23ce5c27b6                      38226520 +- 253606       6      good
android-chrome@23ce5c27b6,chromium@571692      38426883 +- 267938       6      good
android-chrome@23ce5c27b6,chromium@571693      38539523 +- 300272       6      good
android-chrome@23ce5c27b6,chromium@571694      132321368 +- 209665      6      bad       <--
android-chrome@23ce5c27b6,chromium@571698      132107011 +- 466185      6      bad
android-chrome@24cae43d5e                      132381613 +- 166956      6      bad
android-chrome@cd28519e8e                      132130904 +- 409538      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=load.media.imgur system_health.memory_mobile

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8941368842649616496


For feedback, file a bug with component Speed>Bisection