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

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


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

chromium-rel-win8-dual

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

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

Hi hashimoto@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 : Ryo Hashimoto
  Commit : 4e1056461d180f400432dea15d9dce308e3d5740
  Date   : Tue Aug 22 08:33:01 2017
  Subject: arc: Add chrome_content_provider_url_util

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : blink_perf.dom
  Metric       : select-single-remove/select-single-remove
  Change       : 1.89% | 152.335202568 -> 155.209689696

Revision             Result                   N
chromium@496204      152.335 +- 1.78213       6      good
chromium@496229      153.611 +- 0.808658      6      good
chromium@496242      152.218 +- 1.29135       6      good
chromium@496248      150.97 +- 2.19623        6      good
chromium@496251      150.166 +- 1.4684        6      good
chromium@496252      155.731 +- 3.59543       6      bad       <--
chromium@496253      153.911 +- 1.38281       6      bad
chromium@496254      155.21 +- 1.75498        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 blink_perf.dom

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

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


For feedback, file a bug with component Speed>Bisection

The said CL adds utility functions which are built only for Chrome OS, so it should have nothing to do with performance measurements on Windows.

Thanks, rebisecting...

Actually WontFix-ing, this looks too much in the noise.