Thanks again for your insights, Ben. I ended up tracking all weak handles, as well as all allocations, so combining weak handle callbacks with walking all allocations after the isolate has been disposed of seems to cover all memory allocations without any interference from v8 background threads.
Strange, though, that the v8 doesn't provide a way to walk all live memory in an isolate after all contexts are gone or some similar stage. Sounds like a straightforward way to manage resources. . -- -- v8-users mailing list v8-users@googlegroups.com 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 v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
