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

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


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

chromium-rel-win7-dual

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

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

Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : blink_perf.bindings
  Metric       : undefined-first-child/undefined-first-child

Revision             Result                  N
chromium@512389      581.046 +- 380.073      21      good
chromium@512399      529.622 +- 225.943      21      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 --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/8964184247403472528


For feedback, file a bug with component Speed>Bisection

This recovered.