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

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


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

chromium-rel-win7-x64-dual
chromium-rel-win8-dual

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : blink_perf.shadow_dom
  Metric       : v1-large-shallow-distribution/v1-large-shallow-distribution

Revision             Result                     N
chromium@502391      0.321762 +- 0.0425888      21      good
chromium@502481      0.316952 +- 0.0307401      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 blink_perf.shadow_dom

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

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


For feedback, file a bug with component Speed>Bisection

Whatever it was went away, lets close this.