Has this issue been addressed at all? We're running into it now and it 
seems quite frustrating that there isn't just a parameter to properly clean 
up when uninitializing v8.  Even if it's just a debug only setting to help 
us spot leaks/bad code.  

Specifically if something has been placed in the Globals object.  We at 
least seem to be getting weak callbacks with IdleNotification() which seems 
like a hack instead of just calling V8::Dispose( PleaseCallWeakCallbacksNow 
);  I don't even see how this needs to do a GC.  It just needs to run 
through looking for weak object's that have a callback and call it...

-- 
-- 
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.

Reply via email to