Weak Reference proposal
isiahmeadows at gmail.com
Sat Dec 31 13:48:19 UTC 2016
For my particular case, yes it is. Everything mirrored have globally
unique IDs assigned to them, managed independently of the child
process (in most cases), and the state is tied to the ID, not the
value, so I only need a weak reference to clear the backing ID and its
associated state. And reference cycles within the process are
mitigated by the existing mark-and-sweep derivatives engines already
me at isiahmeadows.com
On Tue, Dec 27, 2016 at 4:34 PM, Steve Fink <sphink at gmail.com> wrote:
> On 12/27/2016 04:45 AM, Isiah Meadows wrote:
> The weak reference proposal hasn't seen a lot of activity, and I haven't
> found much news elsewhere on it. What's the status on it?
> Where I'm building a language-integrated process pool in Node.js, complete
> with shared "references" and async iterator support, I really badly need
> weak references to avoid otherwise inevitable memory leaks across multiple
> processes if the references aren't explicitly released. So far, my only
> option is to take a native dependency (I have no other dependencies), but
> that's very suboptimal, and it eliminates the possibility of porting to
> browsers. So I really badly need language-level weak references.
> Would weak references be enough to solve cross-process garbage collection?
> How would you recover a cycle of references among your processes?
> es-discuss mailing list
> es-discuss at mozilla.org
More information about the es-discuss