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

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


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

health-plan-clankium-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/8940070696351443232

=== 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-webview-phone-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:private_footprint_size_avg/browse_social/browse_social_instagram
  Change       : 3.19% | 50241536.0 -> 51845120.0

Revision                                       Result                  N
android-chrome@cd22f0f943                      50241536 +- 675053      6      good
android-chrome@cd22f0f943,chromium@576157      50462037 +- 763855      6      good
android-chrome@cd22f0f943,chromium@576174      49672875 +- 250070      6      good
android-chrome@cd22f0f943,chromium@576178      50297515 +- 416502      6      good
android-chrome@cd22f0f943,chromium@576179      49653760 +- 411836      6      good
android-chrome@cd22f0f943,chromium@576180      51508565 +- 496949      6      bad       <--
android-chrome@cd22f0f943,chromium@576182      51623936 +- 148990      6      bad
android-chrome@cd22f0f943,chromium@576190      51554076 +- 276792      9      bad
android-chrome@c0e3d62ff2                      51845120 +- 417372      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-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.social.instagram 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/8940070696351443232


For feedback, file a bug with component Speed>Bisection