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

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


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

android-one
android-webview-nexus5X
android-webview-nexus6
chromium-rel-mac12
chromium-rel-win10

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

=== 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: winx64_10_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/load_search/load_search_google
  Change       : 11.52% | 11903518.5 -> 13274664.3333

Revision                                 Result                   N
chromium@502790                          11903519 +- 54460.8      6      good
chromium@502806                          12125506 +- 1142695      6      good
chromium@502814                          12065157 +- 1192097      9      good
chromium@502818                          12132522 +- 1141674      6      good
chromium@502820                          12131342 +- 1140272      6      good
chromium@502820,catapult@08d6322ff7      13341573 +- 549165       6      bad       <--
chromium@502821                          13179671 +- 24939.8      6      bad
chromium@502822                          13274664 +- 417544       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=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.search.google system_health.memory_desktop

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8967726439577976704


For feedback, file a bug with component Speed>Bisection