When allocation is forced because we already did two GCs we need to force GCs
authorerik.corry@gmail.com <erik.corry@gmail.com@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Fri, 2 Oct 2009 13:35:37 +0000 (13:35 +0000)
committererik.corry@gmail.com <erik.corry@gmail.com@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Fri, 2 Oct 2009 13:35:37 +0000 (13:35 +0000)
commit4b19c36068cee6a867999f9be00e6b91ac0bdc2e
tree524cb4937d77190fa0d976d1c0677f7a79ba37c6
parente9acdc7a0076fed32fd242a1af9aac5c0d406ebb
When allocation is forced because we already did two GCs we need to force GCs
even if we are attempting to allocate in young space.  There were a few cases
where this wasn't done.  Also misc. changes to make diagnosis of errors like
this one easier.
Review URL: http://codereview.chromium.org/251072

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@3010 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
src/api.cc
src/heap.cc
src/log-utils.cc
src/utils.cc
test/cctest/test-alloc.cc