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

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


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

chromium-rel-win10

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

perf dashboard filed three bugs?

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

Hi xunjieli@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 : Helen Li
  Commit : 05ee1dbfaf0aa7c03b9ea2040f0345277042d0f1
  Date   : Mon Jul 31 13:24:01 2017
  Subject: [wpr-go] Switch system_health_desktop.json to use go

Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:proportional_resident_size_avg/multitab_misc/multitab_misc_typical24
  Change       : 5.91% | 1891139318.17 -> 1779389073.17

Revision             Result                      N
chromium@490745      1891139318 +- 50515292      6      good
chromium@490749      1902407265 +- 41898927      6      good
chromium@490750      1901307644 +- 46245211      6      good
chromium@490751      1810780745 +- 32467706      6      bad       <--
chromium@490753      1800506513 +- 25119500      6      bad
chromium@490760      1789982288 +- 70598546      6      bad
chromium@490774      1779389073 +- 64805462      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=multitab.misc.typical24 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/8972184725041283072


For feedback, file a bug with component Speed>Bisection