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

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


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

chromium-rel-win8-dual

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

=== 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_8_perf_bisect
  Benchmark    : dromaeo.domcorequery
  Metric       : dom/dom
  Change       : 1.22% | 24042.2859549 -> 23749.4555299

Suspected Commit Range
  3 commits in range
  https://chromium.googlesource.com/chromium/src/+log/4863cd0207a8f643205d3c2c4e4ade6c502922b2..bd39182e79f650af547000ea185971a3954419d0


Revision             Result                  N
chromium@510942      24042.3 +- 2483.62      21       good
chromium@510992      24518.0 +- 2749.77      9        good
chromium@511017      24177.1 +- 3121.36      14       good
chromium@511030      24021.2 +- 2046.11      14       good
chromium@511033      23983.9 +- 3097.66      14       good
chromium@511034      ---                     ---      build failure
chromium@511035      ---                     ---      build failure
chromium@511036      23464.7 +- 1426.96      14       bad
chromium@511042      23749.5 +- 1236.51      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 dromaeo.domcorequery

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

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


For feedback, file a bug with component Speed>Bisection

This recovered.