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

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


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

chromium-rel-mac11

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

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

Suspected Commit
  Author : Robert Sesek
  Commit : 5cd8eef498e28e1aacb9109645c001bbbfe1bc26
  Date   : Mon Aug 28 19:51:25 2017
  Subject: [Mac] A potential fix for WaitableEvent::WaitMany on macOS 10.11.

Bisect Details
  Configuration: mac_10_11_perf_bisect
  Benchmark    : thread_times.tough_compositor_cases
  Metric       : thread_browser_cpu_time_per_frame/thread_browser_cpu_time_per_frame
  Change       : 3.31% | 0.756120208375 -> 0.781143022239

Revision             Result                      N
chromium@497844      0.75612 +- 0.00948384       6      good
chromium@497849      0.75466 +- 0.0362662        6      good
chromium@497850      0.78164 +- 0.003421         6      bad       <--
chromium@497851      0.780121 +- 0.00956239      6      bad
chromium@497853      0.778757 +- 0.00246909      6      bad
chromium@497861      0.780526 +- 0.00401734      6      bad
chromium@497877      0.779277 +- 0.0252971       9      bad
chromium@497909      0.780574 +- 0.00251782      6      bad
chromium@497974      0.781143 +- 0.00451882      6      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 thread_times.tough_compositor_cases

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

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


For feedback, file a bug with component Speed>Bisection