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

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


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

chromium-rel-mac11

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

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

Suspected Commit
  Author : Michael Lippautz
  Commit : c56ae86ad852cd0b7af931e42f7ee29308b79574
  Date   : Wed Aug 02 14:02:56 2017
  Subject: Keep WorkerGlobalScope wrapper alive as long as its context is alive

Bisect Details
  Configuration: mac_10_11_perf_bisect
  Benchmark    : blink_perf.bindings
  Metric       : post-message/post-message
  Change       : 34.24% | 58.7643333333 -> 78.8861666667

Revision             Result                  N
chromium@491336      58.7643 +- 3.40574      6      good
chromium@491359      60.0772 +- 2.8436       6      good
chromium@491362      57.4885 +- 4.81936      6      good
chromium@491363      78.0225 +- 3.27692      6      bad       <--
chromium@491364      79.4053 +- 4.54031      6      bad
chromium@491365      78.5107 +- 5.60877      6      bad
chromium@491370      79.4338 +- 4.05046      6      bad
chromium@491381      78.9412 +- 5.47887      6      bad
chromium@491425      78.8862 +- 3.61354      6      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 blink_perf.bindings

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

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


For feedback, file a bug with component Speed>Bisection