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

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


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

android-one

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

=== 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: android_one_perf_bisect
  Benchmark    : blink_perf.dom
  Metric       : modify-element-title/modify-element-title
  Change       : 40.16% | 1524.65188889 -> 2136.98575

Revision             Result                  N
chromium@456320      1524.65 +- 95.5736      9      good
chromium@456322      1489.76 +- 58.7018      6      good
chromium@456323      2116.27 +- 51.656       6      bad       <--
chromium@456324      2146.29 +- 53.7619      6      bad
chromium@456328      2136.99 +- 16.9692      4      bad

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

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

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


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