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

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


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

android-webview-nexus6

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

Actually, I know the reason. It's the fix for the java heap leak.

=== Auto-CCing suspected CL author perezju@chromium.org ===

Hi perezju@chromium.org, 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 : perezju
  Commit : 08d6322ff7a5954b81a0a8024921e59f98efbb12
  Date   : Tue Sep 19 09:03:20 2017
  Subject: [Telemetry] Adjust wait after forcing Garbage Collection

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:java_heap:proportional_resident_size_avg/load_news/load_news_nytimes
  Change       : 60.63% | 9777834.66667 -> 3849557.33333

Revision                                 Result                  N
chromium@502817                          9777835 +- 173239       6      good
chromium@502820                          9969152 +- 231337       6      good
chromium@502820,catapult@08d6322ff7      3993259 +- 39144.8      6      bad       <--
chromium@502821                          4000768 +- 50747.4      6      bad
chromium@502822                          4008277 +- 56061.9      6      bad
chromium@502823                          3837269 +- 55384.4      6      bad
chromium@502829                          3829077 +- 66657.1      6      bad
chromium@502840                          3849557 +- 73366.8      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.news.nytimes 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/8964567973792080816


For feedback, file a bug with component Speed>Bisection