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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgitrZrwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg8tO9vQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgipObogkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg8rOvvwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgipP_swoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg8pf_uwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgiszA_AgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgiqnnrwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgitWSqAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgiszA_AoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgipObogsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgitWSqAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgitOyuwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgit6guQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgirqIsQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgiunwvgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg8pebqgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgiqLUuAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg8rPQswkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgitrZrwkM


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

android-nexus7v2

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

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


===== SUSPECTED CL(s) =====
Subject : Add benchmark that imitates news reading.
Author  : ulan
Commit description:
  
Each story in the benchmark does the following:
1. Load the main page.
2. Open and scroll the first news item.
3. Go back to the main page and scroll it.
4. Open and scroll the second news item.
5. Go back to the main page and scroll it.
6. etc.

This workflow is interesting because it is close to real world
and generates a lot of garbage by creating and discarding pages.

A couple of websites crash with OOM on svelte device, so by
tracking and optimizing for this benchmark we can improve
user experience on low-memory devices.

*** NOTE TO SHERRIF ***
Regressions are expected in system_health.memory_mobile and
system_health.memory_desktop for the following stories:
- load:news:cnn
- load:social:facebook
- load:news:qq
- load:news:reddit
- load:social:twitter

If there are failing tests in form of benchmarks.system_health_smoke_test.SystemHealthBenchmarkSmokeTest.*
please do not revert this CL but instead disabling failing
test by adding them into the _DISABLE_TESTS list in
tools/perf/benchmarks/system_health_smoke_test.py

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

Review-Url: https://codereview.chromium.org/2118293002
Cr-Commit-Position: refs/heads/master@{#405212}
Commit  : 5b1847df818e5be4592e9a6ac4832350bb663023
Date    : Wed Jul 13 17:39:28 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@405201  1235354  6853.92  5  good
chromium@405211  1242726  6853.92  5  good
chromium@405212  2880307  464408   5  bad    <--
chromium@405213  3048243  369133   5  bad
chromium@405214  2369126  7440.75  5  bad
chromium@405216  2705818  465240   5  bad
chromium@405220  2880307  462552   5  bad

Bisect job ran on: android_nexus7_perf_bisect
Bug ID: 628257

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:ashmem:private_dirty_size_avg/load_news_qq
Relative Change: 133.16%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus7_perf_bisect/builds/3076
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9007146637629865808


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

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