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

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


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

chromium-rel-mac-retina
chromium-rel-mac11
chromium-rel-mac11-pro
chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia
win-high-dpi

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

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Please try rerunning the bisect.


If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: mac_10_11_perf_bisect
  Benchmark    : smoothness.top_25_smooth
  Metric       : frame_times/http___www.youtube.com

Revision             Result                   N
chromium@499331      17.9947 +- 0.621796      14      good
chromium@502500      20.9177 +- 3.87819       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 --story-filter=http...www.youtube.com smoothness.top_25_smooth

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

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


For feedback, file a bug with component Speed>Bisection

See https://bugs.chromium.org/p/chromium/issues/detail?id=766624#c6

Bisect unable to find culprit, this regression exists in stable. Ignoring.