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

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


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

android-nexus5X

If I nudge this +1 which makes sense it the range overlaps with  crbug.com/598025  and includes the culprit which is https://codereview.chromium.org/1827183002.

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


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision                Mean Value  Std. Dev.   Num Values  Good?
chromium@383092         0.300909    0.016056    18          good
chromium@383166         0.293593    0.017256    18          bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 599949

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --also-run-disabled-tests thread_times.key_idle_power_cases
Test Metric: thread_total_all_cpu_time_per_second/blank.html
Relative Change: 1.17%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/40
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9016556989969239072


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

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

Trying a bisect on the range mentioned in comment 2.

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


===== SUSPECTED CL(s) =====
Subject : Enable url path fading all on Android configurations.
Author  : tedchoc
Commit description:
  
Previously, this was restricted to document mode, but that is
no longer desired and it should be enabled everywhere.

BUG=597147

Review URL: https://codereview.chromium.org/1827183002

Cr-Commit-Position: refs/heads/master@{#383200}
Commit  : 328129ac349c860993a94ccb1a8944e2f500cc89
Date    : Fri Mar 25 00:30:31 2016


===== TESTED REVISIONS =====
Revision                Mean Value  Std. Dev.   Num Values  Good?
chromium@383166         0.29301     0.010276    5           good
chromium@383199         0.304901    0.007173    5           good
chromium@383200         0.371328    0.026952    5           bad         <-
chromium@383201         0.36036     0.008293    5           bad
chromium@383202         0.37939     0.008581    5           bad
chromium@383205         0.360825    0.016143    5           bad
chromium@383209         0.373319    0.023364    5           bad
chromium@383216         0.358179    0.013843    5           bad
chromium@383231         0.377944    0.018334    5           bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 599949

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --also-run-disabled-tests thread_times.key_idle_power_cases
Test Metric: thread_total_all_cpu_time_per_second/blank.html
Relative Change: 28.99%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/66
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9015919923124595648


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

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