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

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


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

chromium-rel-mac11-pro

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

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

Bisect Details
  Configuration: mac_pro_perf_bisect
  Benchmark    : media.tough_video_cases_tbmv2
  Metric       : story:power_avg/video.html?src_crowd2160.mp4

Revision             Result                  N
chromium@485931      26.8726 +- 6.69325      21      good
chromium@486042      26.2368 +- 1.9747       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.crowd2160.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/8973892753724174336


For feedback, file a bug with component Speed>Bisection

Bisect unable to find any regression, and ref trace has a similar pattern.