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

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


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

chromium-rel-mac11-pro

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

=== 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_tulip2.mp4_seek

Revision             Result                     N
chromium@490140      0.472482 +- 0.0617708      21      good
chromium@490303      0.477384 +- 0.0327346      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.tulip2.mp4.seek 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/8972242535634081136


For feedback, file a bug with component Speed>Bisection