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

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


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

android-webview-nexus6

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

Already recovered. 

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

Hi yosin@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 : yosin
  Commit : 157413286770a7ac5a24c446a30c08f749738276
  Date   : Mon Feb 13 10:55:13 2017
  Subject: Make FrameSelection to hold non-canonicalized DOM positions

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : speedometer
  Metric       : Total/Total
  Change       : 38.19% | 28681.9163889 -> 39634.655

Revision             Result                  N
chromium@449921      28681.9 +- 423.641      6      good
chromium@449927      28806.9 +- 298.14       6      good
chromium@449928      39778.7 +- 330.129      6      bad       <--
chromium@449929      39728.4 +- 369.862      6      bad
chromium@449930      39637.6 +- 282.087      6      bad
chromium@449933      39634.7 +- 295.299      6      bad

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

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

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


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