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

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


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

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

=== 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_chrome:skia:effective_size_avg/load_search/load_search_yandex
  Change       : 12216.00% | 68669.0 -> 8457277.0

Revision                                       Result              N
android-chrome@cd22f0f943                      68669.0 +- 0.0      6      good
android-chrome@cd22f0f943,chromium@576157      68669.0 +- 0.0      6      good
android-chrome@cd22f0f943,chromium@576174      68669.0 +- 0.0      6      good
android-chrome@cd22f0f943,chromium@576178      68669.0 +- 0.0      6      good
android-chrome@cd22f0f943,chromium@576179      68669.0 +- 0.0      6      good
android-chrome@cd22f0f943,chromium@576180      8457277 +- 0.0      6      bad       <--
android-chrome@cd22f0f943,chromium@576182      8457277 +- 0.0      6      bad
android-chrome@cd22f0f943,chromium@576190      8457277 +- 0.0      6      bad
android-chrome@c0e3d62ff2                      8457277 +- 0.0      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.search.yandex 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/8940202138297080496


For feedback, file a bug with component Speed>Bisection