Track JS allocations as they arrive with no affection on performance when tracking is switched off

test/cctest/test-heap.cc

Index: test/cctest/test-heap.cc
diff --git a/test/cctest/test-heap.cc b/test/cctest/test-heap.cc
index 2824d5b242465f2784656c386938750df435ac67..4f97662b44afe3225c553fb2de5ce0dc2bfac65e 100644
--- a/test/cctest/test-heap.cc
+++ b/test/cctest/test-heap.cc
@@ -3229,6 +3229,8 @@ TEST(Regress169928) {
   Factory* factory = isolate->factory();
   v8::HandleScope scope(CcTest::isolate());
 
+  HeapObjectsTracker tracker;

[Hannes Payer (out of office), 2013/10/02 18:00:29]

Why is that here?

[Alexandra Mikhaylova, 2013/10/03 16:27:55]

I used HeapObjectsTracker here to find some untracked allocations that occur
during this test. In fact, HeapObjectsTracker can be used in all tests where JS
allocations are performed.
I've removed it here now as there's a special test for it.

+
   // Some flags turn Scavenge collections into Mark-sweep collections
   // and hence are incompatible with this test case.
   if (FLAG_gc_global || FLAG_stress_compaction) return;