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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6syajwgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgms6dvAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgmtj5rQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgmor3swoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgmrHcswsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6oD3jwgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6qTg9goM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgmuzv5QsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgmtXTvwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6u24-wsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6peZ6QgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgmtyl_gkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6pO2ogsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6s392AgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6tW3iwgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6vCvmgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgmrKM_AsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6v3GwwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgmtWlrgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6qLM3QsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgmoPetAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6pWtiQgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6rGh5AkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgmqHW4QgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6sya9wsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6uPa8QgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgmpbr_AoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgmrHcswkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6uStggsM


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

android-webview-nexus5X

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

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

Suspected Commit
  Author : fgorski
  Commit : 7c52dcabdaefff4b583999c786afbefa907564fb
  Date   : Mon May 15 22:15:20 2017
  Subject: [Android] Adding scheduling through GcmNetworkManager

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:java_heap:proportional_resident_size_avg/background_news/background_news_nytimes
  Change       : 8.76% | 1511936.0 -> 1644373.33333

Revision             Result                  N
chromium@471890      1511936 +- 25239.1      6      good
chromium@471907      1511253 +- 28978.2      6      good
chromium@471915      1504427 +- 31375.8      6      good
chromium@471917      1522005 +- 33044.2      6      good
chromium@471918      1524622 +- 117635       9      good
chromium@471919      1638229 +- 37356.1      6      bad       <--
chromium@471923      1652395 +- 18695.6      6      bad
chromium@471956      1644373 +- 44172.7      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.news.nytimes system_health.memory_mobile

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

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


| 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!