Comment #6 on 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
Revisiting this, I found that it's hard to impossible to completely avoid
side effects, especially with upcoming Proxies etc.
What I can do however is introducing an addition to the V8 API, either a
standalone call or a flag to IdleNotification to force formatting stack
trace strings of of all known error objects on the heap, keeping in mind
that this may cause side effects such as access checks etc. Once the stack
trace string is formatted, the error object would release objects that are
kept alive to do the formatting.
I'm not entirely happy with this approach, but I don't see a good
alternative.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
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/groups/opt_out.
