Why not HeapNumber::kSize instead of 4 * kPointerSize. Shouldn't HeapNumber::kSize be sufficient to cause a GC?
kHeapSize should be enough, but it triggers an assert in Runtime_AllocateInNewSpace that the allocation size must be aligned to kPointerSize. http://codereview.chromium.org/6591073/ -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev
