scriby/asyncblock — Issue #5: asyncblock.enumerator leaks memory if not exhausted
Author: scriby
Created: 2012-01-19 04:48:27+00:00
State: open

If an enumerator isn't fully exhausted, the fiber doesn't appear to be getting garbage collected.

See if there's anything we can do about this, and at the very least add an "abort" method to clean up the enumerator without moving all the way through it.