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

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


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

android-nexus5X

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

===== 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@407380  7817576  116446   8  good
chromium@407384  7844838  20852.5  8  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 631055

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: browse_news-memory:chrome:all_processes:reported_by_chrome:web_cache:effective_size_avg/browse_news_nytimes
Relative Change: 0.76%
Score: 0

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


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

| 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/9005152332299542912

===== 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@407377  7550840  137093   8  good
chromium@407384  7823197  61765.1  8  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 631055

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: browse_news-memory:chrome:all_processes:reported_by_chrome:web_cache:effective_size_avg/browse_news_nytimes
Relative Change: 3.22%
Score: 0

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


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

| 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/9004901227240967072

===== 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@407376  7588502  119283   12  good
chromium@407384  7853057  39630.1  8   bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 631055

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: browse_news-memory:chrome:all_processes:reported_by_chrome:web_cache:effective_size_avg/browse_news_nytimes
Relative Change: 3.45%
Score: 0

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


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

| 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/9004805318136607600

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


===== SUSPECTED CL(s) =====
Subject : [system-health] Tear down the browser after each story in system_health.memory_*
Author  : petrcermak
Commit description:
  
Rationale: Each story should be completely independent as it will allow
us to compare the results from individual stories. As a result, it will
be possible to compare/subtract the results from, e.g.
LOAD:social:facebook and BROWSE:social:facebook.

More importantly, there are literally hundreds of perf dashboard alerts
each time we add a story to the SH story set. This should fix that.

*** NOTE TO PERF SHERIFF ***
This patch will definitely cause a lot of improvements and/or
regressions in system_health.memory_desktop and
system_health.memory_mobile benchmarks. This is expected.

BUG=589726
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:android_s5_perf_cq;master.tryserver.chromium.perf:linux_perf_cq;master.tryserver.chromium.perf:mac_retina_perf_cq;master.tryserver.chromium.perf:winx64_10_perf_cq

Review-Url: https://codereview.chromium.org/2161363004
Cr-Commit-Position: refs/heads/master@{#407380}
Commit  : a30a0719cdc625d240ba75054fc0de1b9f826625
Date    : Sun Jul 24 12:32:33 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@407377  7544210  25610.4  5  good
chromium@407379  7453196  107877   5  good
chromium@407380  7849106  33221.2  5  bad    <--
chromium@407381  7838292  80890.6  5  bad
chromium@407384  7842762  25496.7  5  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 631055

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: browse_news-memory:chrome:all_processes:reported_by_chrome:web_cache:effective_size_avg/browse_news_nytimes
Relative Change: 3.96%
Score: 99.9

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


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

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