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

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


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

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-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

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

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

Hi ulan@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 : 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: win_x64_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/load_games/load_games_lazors
  Change       : 20.48% | 5120000.0 -> 6168576.0

Revision                           Result                 N
chromium@490644                    5120000 +- 0.0         6      good
chromium@490651                    5120000 +- 0.0         6      good
chromium@490652                    5120000 +- 0.0         6      good
chromium@490652,v8@59ddd6061c      5120000 +- 0.0         6      good
chromium@490652,v8@e567dd3ab4      5120000 +- 0.0         6      good
chromium@490652,v8@774a4c5e24      6168576 +- 0.0         6      bad       <--
chromium@490652,v8@4a9718c777      6081195 +- 478607      6      bad
chromium@490653                    6168576 +- 0.0         6      bad
chromium@490654                    6168576 +- 0.0         6      bad
chromium@490657                    6168576 +- 0.0         6      bad
chromium@490669                    6168576 +- 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.games.lazors 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/8972530753026724816


For feedback, file a bug with component Speed>Bisection

 Issue 751042  has been merged into this issue.

 Issue 750821  has been merged into this issue.

 Issue 752058  has been merged into this issue.

 Issue 752533  has been merged into this issue.

 Issue 752878  has been merged into this issue.

Issue 698254 has been merged into this issue.

 Issue 753954  has been merged into this issue.

 Issue 753969  has been merged into this issue.

 Issue 752171  has been merged into this issue.

 Issue 752162  has been merged into this issue.

Regressions are caused by the reverted CL