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

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


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

chromium-rel-mac11

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

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

Hi dalecurtis@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 : Dale Curtis
  Commit : 732ddfe0c3ff211936187e80879a6cef82cdb70b
  Date   : Thu Aug 03 17:51:11 2017
  Subject: Expand no resampling support to Android; cleanup code.

Bisect Details
  Configuration: mac_10_11_perf_bisect
  Benchmark    : media_perftests
  Metric       : audio_bus_to_interleaved/int8_t
  Change       : 38.89% | 20.968075 -> 29.1231833333

Revision             Result                   N
chromium@491782      20.9681 +- 0.281704      6      good
chromium@491783      20.9281 +- 0.157401      6      good
chromium@491784      29.1762 +- 0.322919      6      bad       <--
chromium@491786      29.0316 +- 0.230766      6      bad
chromium@491789      29.2921 +- 0.307867      6      bad
chromium@491795      29.4823 +- 0.332799      6      bad
chromium@491807      29.5624 +- 0.35575       6      bad
chromium@491832      29.5419 +- 0.117479      6      bad
chromium@491881      29.1232 +- 0.312581      6      bad

To Run This Test
  ./src/out/Release/media_perftests --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/8971895425471276656


For feedback, file a bug with component Speed>Bisection

Test is too sensitive to linker differences.