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

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


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

chromium-rel-win7-gpu-nvidia

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

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

Suspected Commit
  Author : Yutaka Hirano
  Commit : 8419e454a81a7e8a625c43caae69d674530f8298
  Date   : Tue Oct 24 12:05:22 2017
  Subject: Have ScriptForbiddenScope work in worker threads

Bisect Details
  Configuration: winx64nvidia_perf_bisect
  Benchmark    : blink_perf.dom
  Metric       : select-multiple-add/select-multiple-add
  Change       : 12.10% | 4261.19562138 -> 3745.38449584

Revision             Result                  N
chromium@511052      4261.2 +- 62.0864       6      good
chromium@511086      4277.35 +- 28.1087      6      good
chromium@511103      4267.44 +- 56.5278      6      good
chromium@511104      3660.36 +- 200.347      6      bad       <--
chromium@511105      3702.64 +- 166.914      6      bad
chromium@511107      3672.27 +- 202.713      6      bad
chromium@511111      3681.76 +- 225.103      6      bad
chromium@511119      3745.38 +- 60.053       6      bad

Please refer to the following doc on diagnosing blink_perf regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/speed/benchmark_harnesses/blink_perf.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 blink_perf.dom

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

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


For feedback, file a bug with component Speed>Bisection