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

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


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

chromium-rel-win7-gpu-ati

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

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


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean    Std Dev  N   Good?
chromium@421452  231000  6314.17  18  good
chromium@421483  230117  7657.05  18  bad

Bisect job ran on: winx64ati_perf_bisect
Bug ID: 651804

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: 0.29%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64ati_perf_bisect/builds/1580
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9000093880750988992


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

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

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

Kicked another bisect

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


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean    Std Dev  N   Good?
chromium@421452  230092  8131.37  18  good
chromium@421483  232764  3261.06  18  bad

Bisect job ran on: winx64ati_perf_bisect
Bug ID: 651804

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: 0.41%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64ati_perf_bisect/builds/1586
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8999815818295371632


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

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

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

Trying again on the Mac instead

===== 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@421423                350632  5887.22  8  good
chromium@421423,v8@0fb486fe44  351040  6191.67  5  good
chromium@421423,v8@42ece47446  365491  7671.14  8  bad    <--
chromium@421424                369791  2732.98  5  bad
chromium@421425                365890  5446.59  8  bad
chromium@421426                369494  2608.35  5  bad
chromium@421428                371491  4040.23  5  bad
chromium@421432                363407  8239.49  8  bad
chromium@421440                369723  3276.14  8  bad
chromium@421457                368524  1688.08  5  bad

Bisect job ran on: mac_10_10_perf_bisect
Bug ID: 651804

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests indexeddb_perf
Test Metric: vm_resident_set_size_final_size_total/vm_resident_set_size_final_size_total
Relative Change: 4.77%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_10_perf_bisect/builds/2417
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8999811430850420592


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

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