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

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


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

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

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: webview-phone-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/load_chrome/load_chrome_blank
  Change       : 10.13% | 10415817.3333 -> 11471390.6667

Suspected Commit Range
  3 commits in range
  https://chromium.googlesource.com/chromium/src/+log/3a3f199d08ab6ec49ff765417936c945c5fae72e..355781b89354303660792752cf9e0c9552d5e875


Revision                                       Result                   N
android-chrome@f9e3d7603e                      10415817 +- 33330.6      6        good
android-chrome@fbe9ad968a                      10510537 +- 66136.2      6        good
android-chrome@fbe9ad968a,chromium@555768      10422132 +- 21102.8      6        good
android-chrome@fbe9ad968a,chromium@555769      ---                      ---      build failure
android-chrome@fbe9ad968a,chromium@555770      ---                      ---      build failure
android-chrome@fbe9ad968a,chromium@555771      11445108 +- 38959.1      6        bad
android-chrome@fbe9ad968a,chromium@555774      11533684 +- 76013.6      6        bad
android-chrome@9af30a5037                      11471391 +- 73347.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-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.chrome.blank 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/8947094822903318848


For feedback, file a bug with component Speed>Bisection

Partial bisect points to something in:
http://test-results.appspot.com/revision_range?start=555768&end=555771&n=1000

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

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

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Hannes Payer
  Commit : c280e7d4f4001ffe6da3d9a7b8658b2cd590e26a
  Date   : Thu May 03 11:43:12 2018
  Subject: [heap] Clear the memory of pooled pages when allocating from the pool.

Bisect Details
  Configuration: webview-phone-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/background_search/background_search_google
  Change       : 3.43% | 29355380.0 -> 30362825.3333

Revision                                                     Result                   N
android-chrome@f9e3d7603e                                    29355380 +- 325240       6      good
android-chrome@fbe9ad968a                                    29532191 +- 320948       6      good
android-chrome@fbe9ad968a,chromium@555768                    29387977 +- 173707       6      good
android-chrome@fbe9ad968a,chromium@555769                    29203999 +- 165611       6      good
android-chrome@fbe9ad968a,chromium@555769,v8@d14bca61b3      29576223 +- 198304       6      good
android-chrome@fbe9ad968a,chromium@555769,v8@c32f661486      29343775 +- 189907       6      good
android-chrome@fbe9ad968a,chromium@555769,v8@90415437fb      29373300 +- 169849       6      good
android-chrome@fbe9ad968a,chromium@555769,v8@c280e7d4f4      30389449 +- 176402       6      bad       <--
android-chrome@fbe9ad968a,chromium@555770                    30288585 +- 103112       6      bad
android-chrome@fbe9ad968a,chromium@555771                    30346612 +- 271190       6      bad
android-chrome@fbe9ad968a,chromium@555774                    30368969 +- 175267       6      bad
android-chrome@fbe9ad968a,chromium@555779                    30521545 +- 85329.2      6      bad
android-chrome@9af30a5037                                    30362825 +- 140767       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=background.search.google 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/8946456233805096368


For feedback, file a bug with component Speed>Bisection

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Hannes Payer
  Commit : c280e7d4f4001ffe6da3d9a7b8658b2cd590e26a
  Date   : Thu May 03 11:43:12 2018
  Subject: [heap] Clear the memory of pooled pages when allocating from the pool.

Bisect Details
  Configuration: clankium-phone-perf-bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/background/after_http_m_youtube_com_results_q_science
  Change       : 2.68% | 33076737.3333 -> 33964204.0

Revision                                                     Result                  N
android-chrome@fbe9ad968a                                    33076737 +- 309966      6      good
android-chrome@fbe9ad968a,chromium@555768                    32961367 +- 285516      6      good
android-chrome@fbe9ad968a,chromium@555769                    33026561 +- 264087      6      good
android-chrome@fbe9ad968a,chromium@555769,v8@d14bca61b3      33120940 +- 377661      6      good
android-chrome@fbe9ad968a,chromium@555769,v8@c32f661486      33060865 +- 295688      6      good
android-chrome@fbe9ad968a,chromium@555769,v8@90415437fb      32997548 +- 170348      6      good
android-chrome@fbe9ad968a,chromium@555769,v8@c280e7d4f4      34118316 +- 179347      6      bad       <--
android-chrome@fbe9ad968a,chromium@555770                    34002092 +- 104661      6      bad
android-chrome@fbe9ad968a,chromium@555771                    33825281 +- 228091      6      bad
android-chrome@fbe9ad968a,chromium@555774                    33986391 +- 322129      6      bad
android-chrome@fbe9ad968a,chromium@555779                    34053804 +- 183008      6      bad
android-chrome@9af30a5037                                    33964204 +- 206530      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=http.m.youtube.com.results.q.science 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/8946456210922566928


For feedback, file a bug with component Speed>Bisection