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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg9La_tAsM


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

chromium-rel-win7-gpu-intel

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

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

Suspected Commit
  Author : meade
  Commit : 3a001533b29c0fe28f2354285b2c2ac8d57d8ce6
  Date   : Mon Mar 13 05:26:20 2017
  Subject: Un-DCHECK-guard ThreadRestrictionVerifier for strings.

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : blink_perf.css
  Metric       : AttributeDescendantSelector/AttributeDescendantSelector
  Change       : 22.40% | 380.472749872 -> 295.232658788

Revision             Result                   N
chromium@456305      380.473 +- 1.34537       6      good
chromium@456316      380.246 +- 3.38495       6      good
chromium@456321      379.873 +- 9.48865       6      good
chromium@456322      379.557 +- 2.9992        6      good
chromium@456323      296.289 +- 0.712969      6      bad       <--
chromium@456324      295.047 +- 1.70715       6      bad
chromium@456326      295.233 +- 2.44935       6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests blink_perf.css

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8985039069867986800

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=4963919568830464


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!