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

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


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

android-nexus6

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2688
Failure reason: the build has failed due to infrastructure failure.

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

=== PERF REGRESSION ===


=== Auto-CCing suspected CL author heimbuef@google.com ===

Hi heimbuef@google.com, the bisect results pointed to your CL, please take a look at the
results.


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


===== SUSPECTED CL(s) =====
Subject : Constrain the zone segment pool size
Author  : heimbuef
Commit description:
  
Added a size constraint to the configuration to limit the segment pool.
This will likely fix the memory alerts from small android devices.

BUG= chromium:655129 

Review-Url: https://chromiumcodereview.appspot.com/2424393002
Cr-Commit-Position: refs/heads/master@{#40476}
Commit  : ef690ca387c116569a2f5dbd71c6f0733a070cc6
Date    : Thu Oct 20 14:48:55 2016


===== TESTED REVISIONS =====
Revision                       Mean     Std Dev  N  Good?
chromium@426566                8375638  119562   8  good
chromium@426590                8406317  91978.2  8  good
chromium@426602                8409498  53154.1  8  good
chromium@426609                8401985  84373.4  8  good
chromium@426610                8405185  77693.3  8  good
chromium@426610,v8@ef690ca387  9073408  156186   5  bad    <--
chromium@426610,v8@5331e3b616  9113631  83774.3  5  bad
chromium@426610,v8@189794ddb2  9089250  61316.0  5  bad
chromium@426611                9073966  224270   5  bad
chromium@426612                9116740  70364.1  5  bad
chromium@426614                9113390  44052.2  5  bad

Bisect job ran on: android_nexus6_perf_bisect
Bug ID: 659064

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.search.yahoo.com.search..ylt.p.google memory.top_10_mobile
Test Metric: memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/foreground/http_search_yahoo_com_search__ylt_p_google
Relative Change: 8.81%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2795
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8994346815230634496


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

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

Looks like heimbuef@ isn't around any more.  Adding verwaest@ as a FYI but closing because all of the metrics recovered (probably because of the activity in https://bugs.chromium.org/p/chromium/issues/detail?id=655129