Revert "Record allocation stack traces".
authorbmeurer@chromium.org <bmeurer@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Tue, 5 Nov 2013 13:46:11 +0000 (13:46 +0000)
committerbmeurer@chromium.org <bmeurer@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Tue, 5 Nov 2013 13:46:11 +0000 (13:46 +0000)
commitb8660f20911898f0948bb89e32ead45f33fbd1f3
treee9c8dd6beb07e7bc948f4a1a7496af45f743b441
parentae8824e5de249f4dc9f60d8cd8edaf731fca824f
Revert "Record allocation stack traces".

This reverts commit r17365 for memory corruption. The issues
are most probably related to storing a filler map without
checking the bump pointer first, and traversing the stack
when called from within a stub (or builtin), while the code
assumes that it's called from a JS function.

R=verwaest@chromium.org

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

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17488 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
src/allocation-tracker.cc [deleted file]
src/allocation-tracker.h [deleted file]
src/heap-snapshot-generator.cc
src/heap-snapshot-generator.h
test/cctest/test-heap-profiler.cc
tools/gyp/v8.gyp