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

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


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

android-nexus6
chromium-rel-mac-retina
chromium-rel-mac11
chromium-rel-mac11-air
chromium-rel-mac11-pro
chromium-rel-mac12
chromium-rel-mac12-mini-8gb
chromium-rel-win10
chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia
chromium-rel-win7-x64-dual
chromium-rel-win8-dual
linux-release
win-high-dpi

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

=== 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_high_dpi_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/load_tools/load_tools_weather
  Change       : 81.19% | 39409891.5556 -> 70983680.0

Revision                                 Result                    N
chromium@502817                          39409892 +- 6946679       9      good
chromium@502820                          38885604 +- 5231216       9      good
chromium@502820,catapult@08d6322ff7      69148672 +- 9342041       6      bad       <--
chromium@502821                          70372011 +- 2019246       6      bad
chromium@502822                          70634155 +- 1419779       6      bad
chromium@502823                          64532025 +- 46494096      9      bad
chromium@502828                          70284629 +- 2532552       6      bad
chromium@502838                          70808917 +- 2839557       6      bad
chromium@502859                          70983680 +- 1816187       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.tools.weather 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/8967792354756909520


For feedback, file a bug with component Speed>Bisection