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

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


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

chromium-rel-mac11-pro

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

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

Bisect Details
  Configuration: mac_pro_perf_bisect
  Benchmark    : media.tough_video_cases
  Metric       : seek/tulip2.wav_seek_warm

Revision             Result                   N
chromium@497694      1.6281 +- 0.787924       21      good
chromium@497727      1.52476 +- 0.649249      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 media.tough_video_cases

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

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


For feedback, file a bug with component Speed>Bisection

Bisect cannot find the perf regression. Mark as WontFix.