Comment #1 on issue 3523 by [email protected]: Deadlock after calling
IdleNotification(100) or Dispose on isolate
http://code.google.com/p/v8/issues/detail?id=3523
I do not really understand the problem you are having. But here are a few
fun facts:
1) What do you mean by memory leak? In JavaScript there is a special class
of memory leak called "live memory leak". This type of leak happens when
you store objects in a global data structure but forget to remove the
reference to them when they are not needed anymore. Hence, these objects
will always be reachable by the garbage collector and will never get
collected.
2) In your scenario, why do you want to perform a garbage collection before
disposing the isolate? The isolate disposal will free all the memory used
by v8 including live and garbage objects.
3) Don't call the garbage collector! This is not recommended. V8 should do
a good job managing the heap memory. However, the IdleNotification is a
hint that the embedder is idle and garbage collection work could be done in
the idle time and LowMemoryNotification is an emergency garbage collection
mechanism when the embedder runs out of memory.
4) I don't see how the deadlock can happen in our source code. We just wait
for sweeper threads if they are active. It seems like the sweeper threads
do not make progress on your platform. It could be a platform configuration
issue on your side.
--
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.
