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

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


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

android-nexus5

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

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

Hi gangwu@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 : [USS] Show USS counters in Types tab
Author  : gangwu
Commit description:
  
Update the commit/update counters for USS

BUG= 328606 

Review-Url: https://codereview.chromium.org/2420213002
Cr-Commit-Position: refs/heads/master@{#427156}
Commit  : 79b625d97774cda6ebf7fe914236bd985cbd002f
Date    : Mon Oct 24 21:26:22 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@427128  1253376  0.0      5  good
chromium@427151  1261568  0.0      5  good
chromium@427154  1265664  0.0      5  good
chromium@427155  1265664  0.0      5  good
chromium@427156  1269760  0.0      5  bad    <--
chromium@427157  1269760  0.0      5  bad
chromium@427162  1269760  0.0      5  bad
chromium@427173  1288602  42131.1  5  bad

Bisect job ran on: android_nexus5_perf_bisect
Bug ID: 659091

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests memory.top_10_mobile_stress
Test Metric: memory:chrome:all_processes:reported_by_os:system_memory:ashmem:proportional_resident_size_avg/background/after_http_yandex_ru_touchsearch_text_science
Relative Change: 2.81%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4281
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8997830872422313616


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

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

Is there a way to re-run the test? It seems my CL is not related to the issue.

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

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


===== SUSPECTED CL(s) =====
Subject : Introduce Layout*::adjustVisualRectForRasterEffects and use it for SVG hairlines.
Author  : chrishtr
Commit description:
  
BUG= 651511 
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
NOTRY=true (added after it passed on all CQ bots except android which failed because of Java heap error)

Review-Url: https://codereview.chromium.org/2444593002
Cr-Commit-Position: refs/heads/master@{#427125}
Commit  : e0679d9453c26e2c2c1de1d3bfefadc7f83a364a
Date    : Mon Oct 24 19:52:23 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@427000  1249280  0.0      5   good
chromium@427100  1249280  0.0      5   good
chromium@427113  1245594  915.893  5   good
chromium@427119  1245184  0.0      5   good
chromium@427122  1245184  0.0      12  good
chromium@427124  1261056  36123.5  12  good
chromium@427125  1265152  33307.6  8   bad    <--
chromium@427150  1261978  915.893  5   bad
chromium@427200  1269760  0.0      5   bad

Bisect job ran on: android_nexus5_perf_bisect
Bug ID: 659091

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http.yandex.ru.touchsearch.text.science memory.top_10_mobile_stress
Test Metric: memory:chrome:all_processes:reported_by_os:system_memory:ashmem:proportional_resident_size_avg/background/after_http_yandex_ru_touchsearch_text_science
Relative Change: 1.64%
Score: 80.0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4327
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8996568901843245072


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

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

It seems this run hit a issue before my check-in.
I should assign this bug to new issue owner, or wait another run which can go through my code?

I'm really sorry about this. Ashmem is a very noisy metric, which explains why the bisects came back incorrect. It wasn't supposed to be monitored, I'm working on fixing that in  bug 664098 .