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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgtsa8pAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg1tCijgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg1u6E7woM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg1tTn6goM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg1sWWoQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg1vae7AgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg1p_puwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg1sXYnggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDglvzqiQgM


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

android-webview-nexus6

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

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

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:java_heap:proportional_resident_size_avg/background/after_http_m_intl_taobao_com_group_purchase_html

Revision             Result                  N
chromium@478934      1918635 +- 250461       21      good
chromium@478951      1938237 +- 84088.0      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 memory.top_10_mobile

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8976709035060263104

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=4514608615784448


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

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

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

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:java_heap:proportional_resident_size_avg/background/after_http_m_intl_taobao_com_group_purchase_html

Revision             Result                  N
chromium@478934      1911272 +- 225734       21      good
chromium@478951      1932239 +- 87220.2      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 memory.top_10_mobile

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8976626856384069232

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=4514608615784448


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

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

These are small regressions, but could be a symptom of a (java heap) leak; trying to bisect again ...

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

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:java_heap:proportional_resident_size_avg/background/after_http_m_youtube_com_results_q_science

Revision             Result                  N
chromium@478934      1875627 +- 246043       21      good
chromium@478951      1900885 +- 77151.9      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 memory.top_10_mobile

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8976301873998467920

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6391430068568064


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

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

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

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:java_heap:proportional_resident_size_avg/background/after_http_m_youtube_com_results_q_science

Revision             Result                  N
chromium@478934      1876017 +- 243856       21      good
chromium@478951      1901666 +- 78933.1      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 memory.top_10_mobile

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8976279557775079888

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6391430068568064


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

The changes are small, and from the bisect results, it seems like the average went up because the "bad" revision is a bit less noisy and lost some of the lower values from the "good" revision.