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

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


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

perf-go-webview-phone

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: go-webview-phone-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:malloc:effective_size_avg/browse_social/browse_social_facebook
  Change       : 0.45% | 24228113.1429 -> 24335978.4286

Revision                       Result                  N
android-chrome@e89c81435e      24228113 +- 167928      21      good
android-chrome@029430f630      24335978 +- 142666      21      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.facebook 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/8940541637565642352


For feedback, file a bug with component Speed>Bisection

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

=== 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    : memory.top_10_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:malloc:effective_size_avg/background/after_http_www_baidu_com_s_word_google
  Change       : 1.27% | 14690446.6667 -> 14877121.3333

Revision                                       Result                   N
android-chrome@e89c81435e                      14690447 +- 51789.3      6      good
android-chrome@029430f630                      14671817 +- 19013.5      6      good
android-chrome@cd22f0f943                      14646572 +- 40402.9      6      good
android-chrome@cd22f0f943,chromium@576157      14679531 +- 9658.47      6      good
android-chrome@cd22f0f943,chromium@576174      14666825 +- 28254.8      6      good
android-chrome@cd22f0f943,chromium@576178      14673149 +- 9330.3       6      good
android-chrome@cd22f0f943,chromium@576179      14674220 +- 14901.2      6      good
android-chrome@cd22f0f943,chromium@576180      14960693 +- 12896.3      6      bad       <--
android-chrome@cd22f0f943,chromium@576182      14965901 +- 8228.98      6      bad
android-chrome@cd22f0f943,chromium@576190      14918873 +- 29789.4      6      bad
android-chrome@c0e3d62ff2                      14954113 +- 13657.7      6      bad
android-chrome@0d971734ae                      14877121 +- 22535.4      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=http.www.baidu.com.s.word.google memory.top_10_mobile

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

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


For feedback, file a bug with component Speed>Bisection