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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgg-TFpQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_f6CuwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_YXl9ggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_f6WpgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgg4j-uwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_e7ntAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_a_ktwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgg4KXuwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgg5n8vQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_Z_9rwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgg_SDvwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_eqd-wkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_d_w4AgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgg_nOpwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgw4ihqQoM


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

android-nexus9

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

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

Hi mattreynolds@chromium.org, the bisect results pointed to your CL below as possibly
causing a regression. Please have a look at this info and see whether
your CL be related.


===== BISECT JOB RESULTS =====
Status: completed


===== SUSPECTED CL(s) =====
Subject : Suppress the Bluetooth prompt when Chrome is launched with BT disabled
Author  : mattreynolds
Commit description:
  
iOS prompts the user to enable Bluetooth when the CBCentralManager object
is created. Setting the ShowPowerAlert option to NO suppresses the prompt.
This allows Chrome to check the Bluetooth enabled state without prompting
the user.

BUG=630769

Review-Url: https://codereview.chromium.org/2443733002
Cr-Commit-Position: refs/heads/master@{#427083}
Commit  : 66b96245fb48c9058056c10267424aee3685bfb1
Date    : Mon Oct 24 16:30:30 2016


===== TESTED REVISIONS =====
Revision         Mean       Std Dev  N   Good?
chromium@427074  109242834  1624122  27  good
chromium@427081  108127886  2438939  41  good
chromium@427082  109924651  1837560  5   good
chromium@427083  105359826  3048063  27  bad    <--
chromium@427084  107835771  2074506  41  bad
chromium@427087  108248113  1705713  27  bad
chromium@427099  108230060  2011680  27  bad
chromium@427123  108446314  1429352  18  bad

Bisect job ran on: android_nexus9_perf_bisect
Bug ID: 660763

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests memory.top_10_mobile_stress
Test Metric: memory:chrome:all_processes:reported_by_os:system_memory:private_dirty_size_avg/foreground/http_en_m_wikipedia_org_wiki_Science
Relative Change: 0.07%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/2221
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8997318256635352304


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5886949947080704

| 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 Tests>AutoBisect.  Thank you!

Only failed on N9s. WontFix.