On Mon, Apr 21, 2014 at 11:15 PM, David Wardell <[email protected]> wrote: > You are a genius. > > I simply placed all the objects (excluding the Isolate) in a sub-block and > then called dispose after this sub-block (thus forcing the other objects' > destructors before the call to Dispose()). > > It even got rid of all the memory leak issues with valgrind. > > Any explanation on what was going on underneath (or better yet a link > explaining whats going on under the hood)? Thank you.
I don't know of any links that explain how this works but it's quite simple, really. Isolates, Contexts, HandleScopes, etc. are things you as a user can nest. You can't exit or destroy V8 before everything has been unwound again. As an analogy: if you think of V8 as a pallet, then it stands to reason that you can't remove the pallet until everything that's been stacked on top of it has been removed. -- -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" 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.
