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

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


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

android-nexus9

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

=== Auto-CCing suspected CL author glebl@chromium.org ===

Hi glebl@chromium.org, the bisect results pointed to your CL below as possibly
causing a regression. Please have a look at this info and see whether
your CL be related.


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


===== SUSPECTED CL(s) =====
Subject : Use LayoutNGBlockFlow for the block layout if layoutNG is enabled.
Author  : glebl
Commit description:
  
BUG=635619

Review-Url: https://codereview.chromium.org/2226033002
Cr-Commit-Position: refs/heads/master@{#410587}
Commit  : 756f6b3cbb4af8b77421d8fea3fa22d07d4c6996
Date    : Tue Aug 09 05:38:18 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@410574  1611366  6211.89  5  good
chromium@410581  1615462  5495.36  5  good
chromium@410584  1616282  7984.57  5  good
chromium@410586  1608090  7440.75  5  good
chromium@410587  1668710  6211.89  5  bad    <--
chromium@410599  1668710  7984.57  5  bad

Bisect job ran on: android_nexus9_perf_bisect
Bug ID: 636353

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

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


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

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

I'm closing this one as WontFix because
1) this graph https://chromeperf.appspot.com/report?sid=85053a1eccad22867d156e16362879bd0ac434ace949960ebae4b8e11f024199&rev=410599 shows that system_health.memory_mobile went back to its normal fluctuation pattern after 411049
2) the suspected patch is related to LayoutNG which is an experimental layout code that is not used in production. So I don't see how it can affect the current perf test coverage.