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

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


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

chromium-rel-win7-gpu-ati

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

=== 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: winx64ati_perf_bisect
  Benchmark    : page_cycler_v2.intl_ar_fa_he
  Metric       : timeToFirstMeaningfulPaint_avg/pcv1-warm/http___www.startimes.com_f.aspx
  Change       : 4.29% | 150.551999993 -> 158.094555557

Revision             Result                  N
chromium@456309      150.552 +- 8.68717      9      good
chromium@456319      152.703 +- 8.44334      9      good
chromium@456322      151.263 +- 6.68624      6      good
chromium@456323      157.33 +- 4.42965       6      bad       <--
chromium@456324      158.692 +- 1.90341      6      bad
chromium@456329      158.095 +- 8.53669      9      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 --story-filter=http...www.startimes.com.f.aspx page_cycler_v2.intl_ar_fa_he

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

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


| 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!