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

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


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

android-webview-nexus6

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

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

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

Suspected Commit
  Author : perezju
  Commit : b5c1738572410f30cbcae23354f1738cf0b222ef
  Date   : Wed Jul 05 08:52:52 2017
  Subject: [Telemetry] Trigger GC on Chrome processes forked from Zygote

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:java_heap:effective_size_avg/foreground/http_yandex_ru_touchsearch_text_science
  Change       : 24.96% | 27313560.5 -> 34130226.3333

Revision                                 Result                   N
chromium@484174                          27313561 +- 3214.76      6      good
chromium@484211                          27313095 +- 975.485      6      good
chromium@484229                          27312963 +- 2062.43      6      good
chromium@484238                          27313216 +- 1560.45      6      good
chromium@484239                          27313244 +- 1868.4       6      good
chromium@484239,catapult@b5c1738572      34128932 +- 39581.1      6      bad       <--
chromium@484240                          34128408 +- 38024.8      6      bad
chromium@484241                          34127644 +- 34313.5      6      bad
chromium@484243                          34130462 +- 28544.6      6      bad
chromium@484247                          34130226 +- 30213.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 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/8974808837779440576


For feedback, file a bug with component Speed>Bisection

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Error: TIMEOUT

The bisect was able to narrow the range, you can try running with:
  good_revision: 28232bff5f48813f417f3d808a68a0858f1765ad
  bad_revision : 88192782118553e9341132cece3a241c241a3b90

If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:java_heap:effective_size_avg/foreground/http_www_amazon_com_gp_aw_s_k_nexus
  Change       : 24.11% | 27516835.3333 -> 34150821.6667

Revision             Result                   N
chromium@484174      27516835 +- 2208.27      6      good
chromium@484211      27517237 +- 1378.17      6      good
chromium@484229      27516818 +- 1110.58      6      good
chromium@484238      27516707 +- 1738.86      6      good
chromium@484241      34158106 +- 9773.55      6      bad
chromium@484243      34154706 +- 30974.9      6      bad
chromium@484247      34150822 +- 22793.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 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/8974808792613479920


For feedback, file a bug with component Speed>Bisection