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

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


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

chromium-rel-win7-dual

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

=== Auto-CCing suspected CL author xhwang@chromium.org ===

Hi xhwang@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Xiaohan Wang
  Commit : f28dc165a6cdec1fd029e7ffe03f5822ec74930d
  Date   : Sat Oct 07 08:01:57 2017
  Subject: (reland) media: Enable CDM host verification in CdmModule

Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : media_perftests
  Metric       : sinc_resampler_convolve/unoptimized_aligned
  Change       : 3.79% | 29855.3123145 -> 28722.9341122

Revision             Result                  N
chromium@507269      29855.3 +- 134.652      6      good
chromium@507280      29852.1 +- 85.1507      6      good
chromium@507285      29851.0 +- 93.6289      6      good
chromium@507288      29848.8 +- 36.6914      6      good
chromium@507289      29811.5 +- 100.614      6      good
chromium@507290      28722.9 +- 1961.74      6      bad       <--

To Run This Test
  .\src\out\Release\media_perftests.exe --single-process-tests

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

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


For feedback, file a bug with component Speed>Bisection

I don't think my CL would affect sinc_resampler_convolve at all. Also, from the graph, it seems the metric has somewhat recovered.

Assign back to jrummell@ for investigation.

Metric has gone back to the previous value, so marking this as done.