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

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


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

chromium-rel-win7-dual

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : v8.browsing_desktop
  Metric       : v8-gc-incremental-step_max/browse_social/browse_social_twitter
  Change       : 33.28% | 6.07704761905 -> 8.09978571429

Suspected Commit Range
  3 commits in range
  https://chromium.googlesource.com/chromium/src/+log/2a8cf486ed032a967e32fd6d76cd519183edc20f..9954327aa6843a506bb77e475336e717bc1db28a


Revision             Result                  N
chromium@499527      6.07705 +- 11.7285      21       good
chromium@499531      5.25364 +- 7.70041      14       good
chromium@499532      6.43457 +- 7.4556       21       good
chromium@499533      ---                     ---      build failure
chromium@499534      ---                     ---      build failure
chromium@499535      8.65357 +- 8.74302      14       bad
chromium@499541      8.09979 +- 6.73987      14       bad

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.social.twitter v8.browsing_desktop

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8969038143440087216


For feedback, file a bug with component Speed>Bisection

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

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to continue

Bisect was stopped because a commit couldn't be classified as either
good or bad.


Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : v8.browsing_desktop
  Metric       : v8-gc-incremental-step_max/browse_social/browse_social_twitter

Revision             Result                  N
chromium@499527      5.84362 +- 10.879       21      good
chromium@499534      6.04552 +- 7.73055      21      unknown
chromium@499541      7.97229 +- 10.7487      21      bad

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.social.twitter v8.browsing_desktop

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8968761023079630624


For feedback, file a bug with component Speed>Bisection

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

Suspected Commit
  Author : Marja Hölttä
  Commit : 36d703778ccd0d2777e0d4b69ed6e65e39a9f521
  Date   : Mon Sep 04 16:05:39 2017
  Subject: [parser] Tentatively enable FLAG_preparser_scope_analysis.

Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : v8.browsing_desktop
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_max/browse_social/browse_social_twitter
  Change       : 8.55% | 45707068.9524 -> 49614262.8571

Revision                           Result                    N
chromium@499527                    45707069 +- 19400343      21      good
chromium@499534                    44874866 +- 13314117      9       good
chromium@499538                    45008018 +- 15120181      14      good
chromium@499538,v8@1c1457fa70      44234069 +- 11486575      9       good
chromium@499538,v8@36d703778c      48003950 +- 12157540      14      bad       <--
chromium@499538,v8@7abdadca0e      52389660 +- 12245863      9       bad
chromium@499539                    50126068 +- 21191936      21      bad
chromium@499540                    49127424 +- 10770259      14      bad
chromium@499541                    49614263 +- 9737209       14      bad

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.social.twitter v8.browsing_desktop

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8968761016255588800


For feedback, file a bug with component Speed>Bisection