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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgpe2f7ggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgpc3I-gkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgleyKpQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgpb3C9gsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg5fqO8AoM


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

chromium-rel-win10
chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia
chromium-rel-win7-x64-dual
chromium-rel-win8-dual

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

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

Hi mlippautz@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] Remove border page
Author  : mlippautz
Commit description:
  
A page now belongs either the nursery *or* the intermediate gen. The page that
contained objects of both spaces is removed in this change.

BUG= chromium:636331 

Review-Url: https://codereview.chromium.org/2209583002
Cr-Commit-Position: refs/heads/master@{#39778}
Commit  : 42ece47446f0dbd3779d6e0e00dce97a1931a9f9
Date    : Tue Sep 27 15:02:22 2016


===== TESTED REVISIONS =====
Revision                       Mean    Std Dev  N  Good?
chromium@421410                208638  389.981  5  good
chromium@421420                208898  1444.29  8  good
chromium@421423                213628  10515.5  8  good
chromium@421423,v8@0fb486fe44  207996  631.449  5  good
chromium@421423,v8@42ece47446  230733  3703.48  8  bad    <--
chromium@421424                228504  8032.17  8  bad
chromium@421425                231581  2526.95  8  bad
chromium@421429                230985  2227.74  5  bad

Bisect job ran on: winx64intel_perf_bisect
Bug ID: 651541

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests indexeddb_perf
Test Metric: vm_working_set_final_size_total/vm_working_set_final_size_total
Relative Change: 10.71%
Score: 99.5

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64intel_perf_bisect/builds/1178
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9000157570021765728


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

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

The CL regressed some more important benchmarks. We are not going to reland for now.