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

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


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

chromium-rel-win7-gpu-nvidia

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

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

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

Revision             Result                    N
chromium@512003      0.72366 +- 0.52096        21      good
chromium@512100      0.730955 +- 0.577885      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/8964198647750527920


For feedback, file a bug with component Speed>Bisection

no bisect, closing as WontFix.