Comment #2 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
Thanks for your reply, but unfortunately your answer didn't help much.
1) I am not really sure what do you mean under "live memory leaks". Perhaps
the Persistent objects which can be created in C++ and available in
JavaScript until I don't call Reset on them. If I am correct this can
happen in two possible ways:
- call Reset directly
- set a weak callback on the given Persistent object which will call Reset
The biggest problem is that if I don't call the IdleNotification method,
the weak callbacks are NEVER get called.
2) I didn't find anywhere a single sentence about the fact that isolate
disposal would free all the memory used by V8. Please, could you link me
anything about that?
Anyway, if I call isolate->Dispose() without calling IdleNotification there
are again two problems:
- If the program ends successfully there are still memory leaks (showed by
Visual Studio on Windows and valgrind on Ubuntu)
- In 50% of the cases the program never stops because of the previously
described deadlock.
3) I would not call it (and neither write this whole issue) if V8 would do
a good garbage collection. In other, maybe older issues, I have read that
garbage collection and removing memory leaks is not 100%-ly guaranteed by
V8. Isn't this still so?
Unfortunately, the truth is that I can't let hang any memory in this
program and this is why I want to do a garbage collection at least at the
end of my program (if GC doesn't get called automatically of course).
4) Do you have any idea what kind of platform configurations can be related
to these sweeper threads? I know that it's hard to find out from such a
little information, but if really this is the only problem which causes the
memory leaks, it must have someone else too.
I am becoming more and more curious how this whole garbage collection works
in V8 and I hope that one day (ASAP) I will also be able to use it to get
rid of ALL memory leaks which I have now (without any deadlocks on Windows).
--
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.
