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

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


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

chromium-rel-win10

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

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

Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : media.desktop
  Metric       : cpu_time_percentage_avg/video.html?src_smpte_3840x2160_60fps_vp9.webm_seek

Revision             Result                    N
chromium@517167      0.730666 +- 0.801972      21      good
chromium@517228      0.768265 +- 0.8224        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=video.html.src.smpte.3840x2160.60fps.vp9.webm.seek media.desktop

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

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


For feedback, file a bug with component Speed>Bisection