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

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


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

health-plan-clankium-phone
health-plan-webview-phone
perf-go-phone-1024
perf-go-phone-512
perf-monochrome-n-phone

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

=== 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: go-phone-1024-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:malloc:allocated_objects_size_avg/browse_chrome/browse_chrome_newtab
  Change       : 11.22% | 85842428.0 -> 95470630.6667

Revision                                       Result                  N
android-chrome@6e5ba20887                      85842428 +- 241658      6      good
android-chrome@23ce5c27b6                      85557915 +- 348677      6      good
android-chrome@23ce5c27b6,chromium@571692      85949113 +- 360821      6      good
android-chrome@23ce5c27b6,chromium@571693      85773015 +- 388924      6      good
android-chrome@23ce5c27b6,chromium@571694      95506179 +- 372322      6      bad       <--
android-chrome@23ce5c27b6,chromium@571698      95725089 +- 200652      6      bad
android-chrome@24cae43d5e                      95481285 +- 325970      6      bad
android-chrome@8dba9381aa                      95470631 +- 362812      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=browse.chrome.newtab 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/8941369159875815632


For feedback, file a bug with component Speed>Bisection