Comment #7 on issue 2340 by yang...@chromium.org: Force format stack traces
for Errors that survived major GC
http://code.google.com/p/v8/issues/detail?id=2340
We already have a weak referencing list on error objects that we need to
format in order to release objects. We are just not taking advantage of it
yet because formatting it after every GC may cause side effects and crash
Chromium for example due to unexpected access checks (the global object may
be destroyed already).
If Chromium knows it wants to have error objects release attached objects,
then it could tell V8 to format those error objects' stack traces, at the
same time making sure that side effects are OK. Then again those side
effects may be observable, something we may not want.
--
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
v8-dev@googlegroups.com
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 v8-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
