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

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


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

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

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

=== 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 : f973fceec6e8eec76f90fa30d33a9a3c13aebf24
  Date   : Wed Jul 18 20:08:24 2018
  Subject: Free fewer resources when idle in oop raster

Bisect Details
  Configuration: go-phone-1024-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/load_news/load_news_wikipedia
  Change       : 142.56% | 5922472.0 -> 14365693.3333

Revision                                       Result                   N
android-chrome@cd22f0f943                      5922472 +- 131730        6      good
android-chrome@cd22f0f943,chromium@576157      5838504 +- 10033.1       6      good
android-chrome@cd22f0f943,chromium@576174      5928616 +- 208711        6      good
android-chrome@cd22f0f943,chromium@576178      5844648 +- 7662.91       6      good
android-chrome@cd22f0f943,chromium@576179      5882877 +- 108754        6      good
android-chrome@cd22f0f943,chromium@576180      14278312 +- 105443       6      bad       <--
android-chrome@cd22f0f943,chromium@576182      14278312 +- 101784       6      bad
android-chrome@cd22f0f943,chromium@576190      14238717 +- 4027.15      6      bad
android-chrome@c0e3d62ff2                      14365693 +- 221902       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.news.wikipedia 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/8940202113970418448


For feedback, file a bug with component Speed>Bisection