Status: Accepted
Owner: ----
CC: [email protected], erik.corry, [email protected]
Labels: Type-Bug Priority-Medium
New issue 2340 by [email protected]: Force format stack traces for
Errors that survived major GC
http://code.google.com/p/v8/issues/detail?id=2340
Issue 2308 took care of releasing raw stack traces after error stack
property was formatted.
However developers still have to be aware that they need to call .stack if
they are planning to keep Error object around otherwise things retained for
lazy formatting might leak.
Viable solution is to force format Error objects that survive major GC. It
is expected that number of such objects would be minimal so force
formatting should not increase pause time.
Our formatting routines are written in JavaScript so Error objects should
be collected during marking step and formatted after GC (e.g. at the point
where we do weak callbacks).
Having a string representation of the stack is better then retaining raw
stack which retains code objects, functions and receivers and might lead to
hard to debug memory leaks.
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
