Updates:
Status: New
Cc: [email protected] [email protected]
Comment #2 on issue 3949 by [email protected]: Object circular leak via
some v8 internals
https://code.google.com/p/v8/issues/detail?id=3949
I will elaborate as the author of the patch.
Fedor asked me to look at some heap dumps - and I noticed that objects in
question have retaining paths ending up in descriptor arrays of the initial
map which is in turn is an initial map for a function cached in the
kApiFunctionCache.
The referred patch prevents promotion of closures into the descriptors, by
preventing usage CONSTANT transition.
That's the difference between:
a.f = function () { };
and
a.f = null;
a.f = function () { };
Another symptom here is that instantiating two socket instances also
resolves the memory leak - most probably because it also prevents the
promotion of closures into descriptor arrays.
I could not quickly create a reduction to ToT V8 - so the problem could
have been resolved on a newer V8 already, but it would be good to have a
confirmation.
--
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.
