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

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


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

android-nexus5X

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

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

Suspected Commit
  Author : dfalcantara
  Commit : 8ef9faffba78738c37df77a160fea80ee5f604af
  Date   : Thu Apr 13 23:30:05 2017
  Subject: 🔍 Update how shared preferences are handled by the widget

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : webrtc.peerconnection
  Metric       : cpu_utilization/720p_call_45s

Revision             Result                       N
chromium@464549      0.056073 +- 9.18879e-05      6      good
chromium@464604      0.0592198 +- 0.016985        6      good
chromium@464605      15.4315 +- 0.8202            6      bad       <--
chromium@464606      15.2311 +- 1.08736           6      bad
chromium@464608      14.7794 +- 1.44208           6      bad
chromium@464611      15.2589 +- 0.73315           6      bad
chromium@464618      15.1051 +- 0.879453          6      bad
chromium@464631      14.9695 +- 1.85527           6      bad
chromium@464658      15.2456 +- 0.942234          6      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 webrtc.peerconnection

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

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


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