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

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


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

chromium-rel-win7-gpu-intel

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

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

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

Revision             Result                   N
chromium@510668      20.8722 +- 0.566681      21      good
chromium@510708      20.8511 +- 0.679486      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=IE.Chalkboard 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/8964860575092417664


For feedback, file a bug with component Speed>Bisection

This is pretty weird, but the ref build had a big spike and bisect can't repro, so hard to dig in further.