Comment #6 on issue 1597 by [email protected]: fail to load v8 at amd64 in the debug mode
http://code.google.com/p/v8/issues/detail?id=1597
I know and totally agree that the context should be disposed in the same thread in an ideal world, but in the real wild world, the Java VM will GC the memory and call the finalizer at any time and from a new finalizer thread. So, if I try to lock the isolate before dispose the context, the isolate may be have been locked by another thread, because the finalizer thread will be schedule at any time. So, I have to choose to use the dirty workaround or leave that memory alone.
What's your suggestion? -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev
