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

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


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

chromium-rel-mac11

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

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

Bisect Details
  Configuration: mac_10_11_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : cpu_time_percentage_avg/load_media/load_media_dailymotion

Revision             Result                     N
chromium@509775      0.281757 +- 0.0168725      21      good
chromium@509872      0.282381 +- 0.0183654      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=load.media.dailymotion system_health.common_desktop

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

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


For feedback, file a bug with component Speed>Bisection

Graphs have since recovered.