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

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


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

chromium-rel-mac-retina

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

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Error: INFRA_FAILURE

The bisect was able to narrow the range, you can try running with:
  good_revision: 108151497c06108c01e9d079372cf3bb62fb7f2b
  bad_revision : 32eca5128a93adada834c1db5de058f540f97d4a

If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: mac_retina_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : cpu_time_percentage_avg/browse_media/browse_media_flickr_infinite_scroll

Revision             Result                      N
chromium@497453      0.285191 +- 0.0393306       11      good
chromium@497519      0.298955 +- 0.00964108      14      bad
chromium@497584      0.301456 +- 0.00621803      9       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 --story-filter=browse.media.flickr.infinite.scroll system_health.common_desktop

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

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


For feedback, file a bug with component Speed>Bisection

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

=== 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: mac_pro_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : cpu_time_percentage_avg/browse_media/browse_media_flickr_infinite_scroll
  Change       : 12.81% | 0.297218104718 -> 0.360512483701

Suspected Commit Range
  3 commits in range
  https://chromium.googlesource.com/chromium/src/+log/aa4c8d53d645e611a5924f130a435e3376eae675..01a170a8595c9ffd7ad144a02a7748db4313ecec


Revision             Result                      N
chromium@497350      0.297218 +- 0.108095        8        good
chromium@497455      0.33613 +- 0.0548455        9        good
chromium@497482      0.33201 +- 0.0768381        13       good
chromium@497483      ---                         ---      build failure
chromium@497484      ---                         ---      build failure
chromium@497485      0.355048 +- 0.0590567       14       bad
chromium@497490      0.36025 +- 0.0187531        9        bad
chromium@497495      0.350321 +- 0.0868282       14       bad
chromium@497508      0.359638 +- 0.00806896      6        bad
chromium@497560      0.360512 +- 0.0161474       9        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 --story-filter=browse.media.flickr.infinite.scroll system_health.common_desktop

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

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


For feedback, file a bug with component Speed>Bisection

Based on my experience, it's not likely that bisect will find a culprit based on the graph of this. WontFix.