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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICglLyNuAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICglPH4pwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICglOPatAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg5NeQqAoM


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

android-nexus6
android-nexus9

Kicked off a few bisects. The graphs are noisy so it might not be easy to track this down.

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


===== SUSPECTED CL(s) =====
Subject : Remove URL path fading from tabbed mode.
Author  : tedchoc
Commit description:
  
BUG= 521178 

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

Cr-Commit-Position: refs/heads/master@{#389560}
Commit  : caa39378ce5da0d3ff191a06c9e162e3b3db7948
Date    : Mon Apr 25 21:04:18 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@389512  29418.4  155.887  5  good
chromium@389557  29568.8  106.373  5  good
chromium@389559  29534.4  99.8639  5  good
chromium@389560  30208.8  149.597  5  bad    <--
chromium@389563  30197.6  124.983  5  bad
chromium@389569  30186.4  102.395  5  bad
chromium@389580  30258.4  58.6924  5  bad
chromium@389602  30224.8  110.613  5  bad

Bisect job ran on: android_nexus9_perf_bisect
Bug ID: 608480

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests webrtc.datachannel
Test Metric: vm_private_dirty_final_browser/vm_private_dirty_final_browser
Relative Change: 2.74%
Score: 99.9

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


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

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

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


===== SUSPECTED CL(s) =====
Subject : Check for 0-length files in ResourceExtractor
Author  : agrieve
Commit description:
  
Also moves from an on-disk version timestamp file to SharedPreferences
(should be faster).

BUG= 606413 

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

Cr-Commit-Position: refs/heads/master@{#390068}
Commit  : b28607d4c72261657ea9e24ea9195bc23a472b3f
Date    : Wed Apr 27 14:44:16 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@390062  35097.7  102.315  6  good
chromium@390065  35067.2  98.1208  5  good
chromium@390067  34986.4  143.9    5  good
chromium@390068  35728.4  143.277  5  bad    <--
chromium@390073  35636.2  139.038  5  bad
chromium@390084  35678.6  56.9588  5  bad
chromium@390106  35696.8  186.809  5  bad

Bisect job ran on: android_nexus6_perf_bisect
Bug ID: 608480

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests page_cycler.intl_ar_fa_he
Test Metric: vm_private_dirty_final_browser/vm_private_dirty_final_browser
Relative Change: 1.76%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2173
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9013147397804440960


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

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

===== 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     Std Dev  N   Good?
chromium@390842  30916.2  296.43   12  good
chromium@390845  30755.3  214.63   12  bad

Bisect job ran on: android_nexus6_perf_bisect
Bug ID: 608480

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests page_cycler.morejs
Test Metric: vm_private_dirty_final_renderer/vm_private_dirty_final_renderer
Relative Change: 0.50%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2174
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9013147389881784048


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

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