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

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


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

chromium-rel-win7-gpu-intel

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

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

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : cpu_time_percentage_avg/browse_media/browse_media_youtube

Revision             Result                     N
chromium@518614      0.190553 +- 0.0598071      21      good
chromium@518676      0.193104 +- 0.0512194      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=browse.media.youtube 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/8962043591487511168


For feedback, file a bug with component Speed>Bisection

It looks like this metric returned to normal within Chromium Commit Position range 519497 - 519593