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

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


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

chromium-rel-win7-dual

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

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

Hi jgruber@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 : Jakob Gruber
  Commit : ddb5255f59734c09964b84782e072cb663f3a67e
  Date   : Mon Sep 11 16:47:06 2017
  Subject: Reland "[snapshot] Temporarily enable --lazy-deserialization"

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_social/load_social_vk
  Change       : 4.83% | 6643712.0 -> 6322858.66667

Revision                           Result                 N
chromium@500979                    6643712 +- 0.0         6      good
chromium@501003                    6643712 +- 0.0         6      good
chromium@501009                    6643712 +- 0.0         9      good
chromium@501010                    6585458 +- 494303      9      good
chromium@501010,v8@35be2798fb      6647808 +- 0.0         6      good
chromium@501010,v8@8340a86a62      6647808 +- 0.0         6      good
chromium@501010,v8@ddb5255f59      6410240 +- 0.0         6      bad       <--
chromium@501011                    6410240 +- 0.0         9      bad
chromium@501012                    6410240 +- 0.0         6      bad
chromium@501015                    6410240 +- 0.0         6      bad
chromium@501027                    6322859 +- 478607      6      bad
chromium@501074                    6322859 +- 478607      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=load.social.vk 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/8968403012182696448


For feedback, file a bug with component Speed>Bisection