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

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


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

chromium-rel-win8-dual

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

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

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : smoothness.tough_path_rendering_cases
  Metric       : frame_times/IE Chalkboard

Revision             Result                  N
chromium@499364      21.9141 +- 20.3061      21      good
chromium@499387      20.803 +- 1.78103       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 --story-filter=IE.Chalkboard smoothness.tough_path_rendering_cases

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

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


For feedback, file a bug with component Speed>Bisection

This recovered.