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

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


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

chromium-rel-win10

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

=== 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: winx64_10_perf_bisect
  Benchmark    : media_perftests
  Metric       : audio_converter/convert
  Change       : 0.24% | 105565.014266 -> 105407.457621

Suspected Commit Range
  2 commits in range
  https://chromium.googlesource.com/chromium/src/+log/052eb922589a2d785ea451e3f603d9d3aa425a7d..54526ffcba714c1106181235cb63fdbb2aee3fbb


Revision             Result                 N
chromium@486329      105565 +- 852.402      14       good
chromium@486333      105675 +- 315.5        6        good
chromium@486336      105592 +- 531.872      14       good
chromium@486337      ---                    ---      build failure
chromium@486338      105405 +- 775.43       21       bad
chromium@486346      105315 +- 512.964      14       bad
chromium@486364      105382 +- 557.988      14       bad
chromium@486397      105407 +- 860.17       14       bad

To Run This Test
  .\src\out\Release_x64\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/8973706475829451824


For feedback, file a bug with component Speed>Bisection

These CL look completely unrelated, and the "result" section of the bisect looks inconclusive at best.