Status: New
Owner: ----
New issue 3949 by [email protected]: Object circular leak via some v8
internals
https://code.google.com/p/v8/issues/detail?id=3949
Version: 4.1.0.21
OS: Any
Architecture: x64, but likely others too
What steps will reproduce the problem?
1. git clone https://github.com/indutny/io.js.git -b test/v8-team-circular
--depth 1
2. cd io.js && ./configure && make -j9
3. wget
https://gist.githubusercontent.com/indutny/f6cb78564f630948563a/raw/8fccb34e7b1ed3fb5276088ad9241dc6b6aee914/test.js
4. ./out/Release/iojs test.js
What is the expected output?
"destroyed" string in stderr
What do you see instead?
Nothing
However, if I'll apply this patch:
https://gist.github.com/mraleph/ac9c56905a18bbb391d8 or remove circular
references from TLSWrap to JSStream and vice versa - TLSWrap instance will
be collected.
I suppose there is some implicit reference in internals which prevents this
TLSWrap <=> JSStream circular reference from being collected. Both of them
are in independent weak Persistent handles, and ideally should be easily
collected.
--
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.
