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

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


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

chromium-rel-win8-dual

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

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

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : smoothness.gpu_rasterization.tough_path_rendering_cases
  Metric       : frame_times/MotionMark Canvas Stroke Shapes

Revision             Result                  N
chromium@507377      46.1067 +- 3.57222      21      good
chromium@507444      45.669 +- 2.2236        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=MotionMark.Canvas.Stroke.Shapes smoothness.gpu_rasterization.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/8965451811392736928


For feedback, file a bug with component Speed>Bisection

No culprit found. The graph is too noisy and the change is within the CI.