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

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


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

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

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

Bisect Details
  Configuration: go-webview-phone-perf-bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:private_footprint_size_avg/foreground/https_m_facebook_com_rihanna
  Change       : 1.15% | 22328271.2381 -> 22585734.0952

Revision                       Result                  N
android-chrome@74662f91c8      22328271 +- 365038      21      good
android-chrome@1032e70048      22585734 +- 384324      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=https.m.facebook.com.rihanna 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/8940099929274964720


For feedback, file a bug with component Speed>Bisection

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

=== Auto-CCing suspected CL author clank-buildbot@google.com ===

Hi clank-buildbot@google.com, 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 : clank-autoroller
  Commit : 4e67b217c5ff5351383e0a7b15294583c4c4b7cd
  Date   : Wed Jul 18 09:03:01 2018
  Subject: Roll to 575954

Bisect Details
  Configuration: go-phone-1024-perf-bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:private_footprint_size_avg/foreground/http_search_yahoo_com_search__ylt_p_google
  Change       : 0.91% | 38972074.6667 -> 39327158.8571

Revision                                       Result                  N
android-chrome@74662f91c8                      38972075 +- 321564      21      good
android-chrome@1032e70048                      39004843 +- 271821      9       good
android-chrome@1032e70048,chromium@575954      39033060 +- 217215      9       good
android-chrome@4e67b217c5                      39500004 +- 325104      9       bad       <--
android-chrome@478583399d                      39327159 +- 341117      14      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=http.search.yahoo.com.search..ylt.p.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/8940074511339728864


For feedback, file a bug with component Speed>Bisection

Assigned, but no owner or component? Please find a component and/or owner