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

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


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

chromium-rel-win8-dual

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

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

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : scheduler.tough_scheduling_cases
  Metric       : queueing_durations/sync_scroll_offset.html

Revision             Result                    N
chromium@514694      0.118305 +- 0.979252      21      good
chromium@514780      0.118269 +- 0.791211      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=sync.scroll.offset.html scheduler.tough_scheduling_cases

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

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


For feedback, file a bug with component Speed>Bisection

False alert, the ref moved at the same time.

WontFix-ing per #4