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

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


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

android-nexus6
android-nexus7v2
chromium-rel-mac-retina
chromium-rel-mac11-air
chromium-rel-mac11-pro
chromium-rel-mac12
chromium-rel-win10
chromium-rel-win7-dual
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/8967792294071333536

=== 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:allocated_objects_size_avg/load_tools/load_tools_weather
  Change       : 50.33% | 30687872.0 -> 46133340.0

Revision                                 Result                   N
chromium@502817                          30687872 +- 3580622      6      good
chromium@502820                          30794097 +- 3498614      6      good
chromium@502820,catapult@08d6322ff7      47564581 +- 2960754      6      bad       <--
chromium@502821                          46905116 +- 5330373      6      bad
chromium@502822                          46108296 +- 3898836      6      bad
chromium@502823                          47304156 +- 1408609      6      bad
chromium@502828                          47010312 +- 2271452      6      bad
chromium@502838                          47122061 +- 2283858      6      bad
chromium@502859                          46133340 +- 2680727      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/8967792294071333536


For feedback, file a bug with component Speed>Bisection