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

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


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

chromium-rel-win7-dual

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to continue

Bisect was stopped because a commit couldn't be classified as either
good or bad.


Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : media_perftests
  Metric       : audio_bus_from_interleaved/int16_t

Revision             Result                   N
chromium@495827      14.0003 +- 0.208248      21      good
chromium@495829      13.9784 +- 0.19587       21      unknown
chromium@495831      13.9402 +- 0.350352      21      bad
chromium@495834      13.938 +- 0.412315       21      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/8970617398065743744


For feedback, file a bug with component Speed>Bisection

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

Comment 4 is a new bisect with wider range.

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : media_perftests
  Metric       : audio_bus_from_interleaved/int16_t
  Change       : 1.37% | 13.8523416667 -> 13.9843111111

Suspected Commit Range
  8 commits in range
  https://chromium.googlesource.com/chromium/src/+log/72f8c23709f8159233eba6c1bfa2ed76bc825d3a..6dee06cc08d9147aed4978b1239b034c9889f67e


Revision             Result                   N
chromium@495808      13.8523 +- 0.105273      6        good
chromium@495831      13.8953 +- 0.367051      14       good
chromium@495832      13.8993 +- 0.240765      14       good
chromium@495833      ---                      ---      build failure
chromium@495834      ---                      ---      build failure
chromium@495835      ---                      ---      build failure
chromium@495836      ---                      ---      build failure
chromium@495837      ---                      ---      build failure
chromium@495838      ---                      ---      build failure
chromium@495839      ---                      ---      build failure
chromium@495840      13.9997 +- 0.205978      14       bad
chromium@495842      13.9905 +- 0.170757      14       bad
chromium@495853      13.9843 +- 0.265286      9        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/8970607729689120992


For feedback, file a bug with component Speed>Bisection

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

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

Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : media_perftests
  Metric       : audio_bus_from_interleaved/int16_t

Revision             Result                   N
chromium@495816      13.9815 +- 0.221734      21      good
chromium@495839      13.9537 +- 0.273503      21      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/8970535481027657296


For feedback, file a bug with component Speed>Bisection