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

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


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

chromium-rel-mac-retina
chromium-rel-mac11-pro
chromium-rel-win10

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

=== 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: winx64_10_perf_bisect
  Benchmark    : smoothness.top_25_smooth
  Metric       : percentage_smooth/http___www.youtube.com

Revision             Result                  N
chromium@499354      56.523 +- 8.90354       14      good
chromium@502497      46.2166 +- 11.1313      14      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=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/8968031043453986320


For feedback, file a bug with component Speed>Bisection

This looks like the same problem as  crbug.com/766515 , in that the 2 reference values work but the benchmark is broken for a large portion of the range (and that range is huge). It keeps testing revisions trying to find a working one until eventually it hits the 24 hour limit.

Blocking on crbug.com/674945 for improving the output when it hits the 24 hour limit.

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