Reviewers: Hannes Payer,
Description:
Attempt no. 3 to fix Heap::IsHeapIterable and HeapIterator.
Now we remember new space's top pointer after the last GC to find out if
there
was a new space allocation since the last GC.
Unfortunately, this not completely safe - the debugger has a callback hook
(that
can call to JS) at the end of the GC epilogue that can in theory allocate
and
possibly make the heap non-iterable. We can only hope this does not happen.
BUG=373283
[email protected]
LOG=N
Please review this at https://codereview.chromium.org/291193005/
SVN Base: https://v8.googlecode.com/svn/branches/bleeding_edge
Affected files (+91, -79 lines):
M src/debug.cc
M src/heap.h
M src/heap.cc
M src/heap-profiler.cc
M src/heap-snapshot-generator.cc
M src/liveedit.cc
M src/runtime.cc
M test/cctest/test-api.cc
M test/cctest/test-heap.cc
M test/cctest/test-object-observe.cc
A test/mjsunit/regress/regress-373283.js
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
