Some tests involving AllocationSites are failing in GcStress test mode.
authormvstanton@chromium.org <mvstanton@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Wed, 17 Jul 2013 11:42:32 +0000 (11:42 +0000)
committermvstanton@chromium.org <mvstanton@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Wed, 17 Jul 2013 11:42:32 +0000 (11:42 +0000)
commit7632a311aa88e1cd565ae6af10d70a0ccb32bc5e
tree463bc0147e7004ad7f062c3140a02e0f9f937bbf
parent410b4b2db48854bcd6561919a4d97a02c9564630
Some tests involving AllocationSites are failing in GcStress test mode.
The reason is that an AllocationMemento associated with an array only
lives for one gc (it is unrooted). So an excess of garbage collections
in these tests cause the Memento to be lost, and expected behavior
can't be guaranteed.

BUG=
R=hpayer@chromium.org

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

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@15714 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
test/mjsunit/array-constructor-feedback.js
test/mjsunit/array-feedback.js