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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICggOqRrwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICggNGFswoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICggIm_vgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgwOjVpQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICggJWpuwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgwNyIrAoM


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

android-galaxy-s5
android-nexus5
android-nexus7v2
android-one

Kicked off bisect for this since my variations change was in range.

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

Hi keishi@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 : Add threshold for V8Followup-IdleGC
Author  : keishi
Commit description:
  
The V8Followup-IdleGC seems to be triggering a lot of GCs with low collection count.

BUG=None

Review URL: https://codereview.chromium.org/1782833005

Cr-Commit-Position: refs/heads/master@{#380607}
Commit  : d2466040fdea5f25406f9c6ac07efab10c46548d
Date    : Fri Mar 11 12:20:11 2016


===== TESTED REVISIONS =====
Revision                Mean Value  Std. Dev.   Num Values  Good?
chromium@380605         12666.666667336.725407  9           good
chromium@380606         12837.5     101.978989  8           good
chromium@380607         13431.5     324.4437    8           bad
chromium@380609         13495.2     371.326272  5           bad
chromium@380612         13391.5     356.04454   8           bad
chromium@380619         13601.0     90.503354   8           bad

Bisect job ran on: android_s5_perf_bisect
Bug ID: 594435

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --also-run-disabled-tests webrtc.getusermedia
Test Metric: vm_private_dirty_final_renderer/vm_private_dirty_final_renderer
Relative Change: 7.31%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_bisect/builds/524
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9018102213155643040


| 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 label Cr-Tests-AutoBisect.  Thank you!

based on comment#3, keishi@ could you please check the issue.

keishi: ping

r380607 decreased the occurance of BlinkGC, thus it is expected that the memory usage at the end of the test might increase. There should be no problem unless it increases the peack memory usage.

Marking as WontFix.