Sven, This problem keeps biting embedders over and over and over. Even if Chrome does not need it... The rest of the world needs a way to GUARANTEE that C++ backed JS objects get destroyed in a reliable and predicable manner.
There are many hacks people use to try to get weak callbacks to fire. This is just another attempt. Can you or anyone propose a mechansim for fixing this? I would be happy to attempt implementation if a decent proposal would come forward for: 1) Guaranteeing weak callbacks for all objects fire on shutdown of V8. (necessary for proper memory leak testing) 2) A mechansim for telling V8 to collect garbage and fire weak callbacks on demand. If we don't fix this right, everyone and their uncle will be using this "solution"... We have no other choice. Mike M. -- -- 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/groups/opt_out.
