async seems to keep port writers alive

[doudou]

The non-block version of InputPort#writer calls #proxy_event on the port object, thus adding a reference from the port to the writer object. This avoids garbage collection of the writer, and thus creates a memory leak.

I guess that the same issue exists for the readers.

My gut feeling is that it could be fixed by making sure that #proxy_event uses WeakRef to reference the proxied objects.

[D-Alex]

The reference is used to propagate errors from the reader/writer to the port. I guess we could change the code to do the propagation from the reader/writer side

[doudou]

The issue is that I've seen this pattern quite a few times, that's why I was wondering about moving to a WeakRef implementation instead (it makes sure we don't get the problem ...). But it is also more changes, and only the reader/writer stuff is problematic from a ressource point of view (they maintain a connection to the port).