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

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


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

chromium-rel-win10
chromium-rel-win7-dual
chromium-rel-win7-gpu-ati

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

=== 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_games/load_games_alphabetty

Revision             Result                  N
chromium@490615      8718629 +- 1085379      21      good
chromium@490644      8643730 +- 840731       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.games.alphabetty 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/8972264869802365840


For feedback, file a bug with component Speed>Bisection

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

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Ulan Degenbaev
  Commit : 774a4c5e240569b551cc9d19ae8cac146891d4c4
  Date   : Fri Jul 28 19:42:31 2017
  Subject: Revert "[heap] Reland "[heap] Allow a minimum semi-space size of 512K.""

Bisect Details
  Configuration: winx64nvidia_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/load_news/load_news_hackernews
  Change       : 11.41% | 4595712.0 -> 5120000.0

Revision                           Result              N
chromium@490645                    4595712 +- 0.0      6      good
chromium@490651                    4595712 +- 0.0      6      good
chromium@490652                    4595712 +- 0.0      6      good
chromium@490652,v8@59ddd6061c      4595712 +- 0.0      6      good
chromium@490652,v8@e567dd3ab4      4595712 +- 0.0      6      good
chromium@490652,v8@774a4c5e24      5120000 +- 0.0      6      bad       <--
chromium@490652,v8@4a9718c777      5120000 +- 0.0      6      bad
chromium@490653                    5120000 +- 0.0      6      bad
chromium@490654                    5120000 +- 0.0      6      bad
chromium@490657                    5120000 +- 0.0      6      bad
chromium@490669                    5120000 +- 0.0      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.news.hackernews 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/8971268552644715248


For feedback, file a bug with component Speed>Bisection