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

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


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

chromium-rel-mac-retina
chromium-rel-mac11-pro
chromium-rel-win10
chromium-rel-win7-dual
chromium-rel-win7-gpu-nvidia

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/load_media/load_media_imgur

Revision             Result                    N
chromium@490727      33335198 +- 13240836      21      good
chromium@490763      35332486 +- 9765733       21      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 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.media.imgur 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/8972283168914262480


For feedback, file a bug with component Speed>Bisection

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

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

Error: INFRA_FAILURE

The bisect was able to narrow the range, you can try running with:
  good_revision: a466241d2016898dfe2bf4218d72b7de04966165
  bad_revision : 7cfb8d0d59aaf783845accc7d41a5a63f9413c2c

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


Bisect Details
  Configuration: mac_10_12_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/load_tools/load_tools_docs

Revision             Result                    N
chromium@490749      74821651 +- 9644858       21       good
chromium@490751      ---                       ---      build failure
chromium@490752      76587924 +- 5877457       14       bad
chromium@490754      79213285 +- 15609006      9        bad
chromium@490759      76695475 +- 4738738       9        bad
chromium@490769      77761535 +- 2333646       6        bad
chromium@490788      77323328 +- 3232889       6        bad
chromium@490826      76416019 +- 8001553       21       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 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.tools.docs 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/8970630321914832448


For feedback, file a bug with component Speed>Bisection

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

=== 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: mac_10_12_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/browse_news/browse_news_flipboard
  Change       : 53.27% | 84046860.6667 -> 128819592.0

Revision             Result                    N
chromium@490749      84046861 +- 1620403       6      good
chromium@490750      84342747 +- 518764        6      good
chromium@490751      128663140 +- 2371630      6      bad       <--
chromium@490752      128991905 +- 1004405      6      bad
chromium@490754      128287332 +- 1329830      6      bad
chromium@490759      128291018 +- 778365       6      bad
chromium@490769      128414426 +- 1018748      6      bad
chromium@490788      128772350 +- 2871465      6      bad
chromium@490826      128819592 +- 1734990      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 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.flipboard 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/8969847031529285376


For feedback, file a bug with component Speed>Bisection