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

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


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

android-one

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

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

Hi hpayer@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 : [heap] Always use the passed-in collector in CollectGarbage.
Author  : hpayer
Commit description:
  
Do not overwrite a collector decision.

BUG=

Review-Url: https://codereview.chromium.org/2336943003
Cr-Commit-Position: refs/heads/master@{#39585}
Commit  : c19abaddafb5ede5e0d5efbe608b7fc5d7c7fcd0
Date    : Wed Sep 21 09:57:08 2016


===== TESTED REVISIONS =====
Revision                       Mean     Std Dev  N  Good?
chromium@420135                20.2515  9.38956  5  good
chromium@420147                29.0847  13.8666  5  good
chromium@420150                30.5613  15.9176  5  good
chromium@420151                37.7834  38.6022  5  good
chromium@420151,v8@06c6591d0f  27.9793  31.4308  5  good
chromium@420151,v8@c19abaddaf  182.946  25.9756  5  bad    <--
chromium@420151,v8@2fd6d6093e  183.494  20.6335  5  bad
chromium@420152                183.277  28.7906  5  bad
chromium@420153                189.483  29.2827  5  bad
chromium@420159                167.0    25.8039  5  bad

Bisect job ran on: android_one_perf_bisect
Bug ID: 649361

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests v8.infinite_scroll-ignition_tbmv2
Test Metric: v8-gc-latency-mark-compactor_max/v8-gc-latency-mark-compactor_max
Relative Change: 724.63%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/builds/1633
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9000807772005572240


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

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

Reverting the CL in #3 fixed this problem. Leaving this bug open until we know why the memory regression actually happened.

hpayer@: is there any update? Also did you land your revert?

Ping. This has been open for a while. hpayer@, any updates?

Due to revert in #3.