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

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


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

chromium-rel-mac11-pro

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

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

Bisect Details
  Configuration: mac_pro_perf_bisect
  Benchmark    : media.tough_video_cases_tbmv2
  Metric       : cpu_time_percentage_avg/video.html?src_crowd1080.mp4

Revision             Result                     N
chromium@489660      0.254961 +- 0.0189129      21      good
chromium@489763      0.256964 +- 0.0124155      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 --story-filter=video.html.src.crowd1080.mp4 media.tough_video_cases_tbmv2

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

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


For feedback, file a bug with component Speed>Bisection

Bisect didn't find a culprit, and now the regression is stale.