Skip to content

asyncblock.enumerator leaks memory if not exhausted #5

scriby opened this Issue Jan 19, 2012 · 0 comments

1 participant

scriby commented Jan 19, 2012

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.

@scriby scriby was assigned Jan 19, 2012
@scriby scriby pushed a commit that closed this issue May 12, 2012
Chris Scribner Fixes #5
Get rid of memory leak if the enumerator is not enumerated
@scriby scriby closed this in 3c4b975 May 12, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.