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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICghsHy7QgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgxrCppwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgxqj8pQoM


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

android-nexus9

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

===== 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@408196  12915200  799104   8  good
chromium@408246  11334656  932876   8  bad

Bisect job ran on: android_nexus9_perf_bisect
Bug ID: 633227

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests system_health.memory_mobile
Test Metric: load_search-memory:chrome:all_processes:reported_by_os:system_memory:java_heap:private_dirty_size_avg/load_search_yahoo
Relative Change: 14.03%
Score: 0

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


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

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

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

===== 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@408116  12754432  339939   8  good
chromium@408341  13142016  80175.2  8  bad

Bisect job ran on: android_nexus9_perf_bisect
Bug ID: 633227

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests system_health.memory_mobile
Test Metric: load_news-memory:chrome:all_processes:reported_by_os:system_memory:java_heap:private_dirty_size_avg/load_news_hackernews
Relative Change: 2.39%
Score: 0

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


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

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

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

===== 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@407875  12584448  150798   8  good
chromium@408246  12829696  801743   8  bad

Bisect job ran on: android_nexus9_perf_bisect
Bug ID: 633227

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests system_health.memory_mobile
Test Metric: load_news-memory:chrome:all_processes:reported_by_os:system_memory:java_heap:private_dirty_size_avg/load_news_hackernews
Relative Change: 0.44%
Score: 0

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


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

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

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

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


===== SUSPECTED CL(s) =====
Subject : [Android] Roll support lib to 24.1.1
Author  : ianwen
Commit description:
  
This is the second attempt to roll the support library. The first
attempt was https://codereview.chromium.org/2175513002 and it was
reverted in https://codereview.chromium.org/2175763003 due to downstream
bots failure.

BUG=629768

Review-Url: https://codereview.chromium.org/2185133002
Cr-Commit-Position: refs/heads/master@{#408211}
Commit  : c8ba82433d4b45be103fc3f3b0005d6df5c82a64
Date    : Wed Jul 27 19:18:31 2016


===== TESTED REVISIONS =====
Revision         Mean      Std Dev  N  Good?
chromium@408196  11920179  89476.7  5  good
chromium@408209  11916083  72835.1  5  good
chromium@408210  11874304  91176.3  5  good
chromium@408211  12480512  62589.8  5  bad    <--
chromium@408212  12500992  174645   5  bad
chromium@408215  12505088  148109   5  bad
chromium@408221  12491162  34707.4  5  bad
chromium@408246  12410880  88230.5  5  bad

Bisect job ran on: android_nexus9_perf_bisect
Bug ID: 633227

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests system_health.memory_mobile
Test Metric: load_games-memory:chrome:all_processes:reported_by_os:system_memory:java_heap:private_dirty_size_avg/load_games_lazors
Relative Change: 4.12%
Score: 99.9

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


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

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