Yes, if the stack walker could follow any breadcrumb trail that GC leaves, and/or do a best effort that would be good.
I am seeing it fail in EvacuateNewSpace about 1 in 10 when I force an out-of-memory. So I guess folks may be seeing this out in the real world too. No intention of continuing to execute JavaScript code of course, but a stack trace can be very handy. The out-of-memory may not be the fault of the current running code, but it can be a useful clue, and usually worth a look. -- -- 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.
