Comment #8 on issue 3523 by [email protected]: Deadlock after calling
IdleNotification(100) or Dispose on isolate
https://code.google.com/p/v8/issues/detail?id=3523
Just a final note regarding #6 ("... the only thing I can do: .."): This is
*not* the only thing you can do, quite the opposite: The only safe way to
get timely deallocation is to design your API on the JavaScript side right.
Concretely, in addition to a constructor you need some explicit form
of "destructor" for your objects on the JavaScript side.
As an example: If you want to expose e.g. C's FILE* I/O on the JavaScript
side, you need some explicit "close" function, too, not only an "open".
Relying on the garbage collector to close some file descriptors would be a
recipe for trouble, because file descriptors are normally a scarce
resource, so you really, really want to close them explicitly as soon as
possible.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" 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.
