ZIO Stream: Eagerly Release Resources in ZStream.aggregateAsync #7256
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves #7235.
The basic structure of this operator is that we repeatedly race the sink fiber and the schedule fiber.
As the sink fiber is being run repeatedly and produces its summary value each time there is no need to extend the scope of resources acquired by the sink into the scope of the stream and in fact doing so creates a memory leak.
In addition, we should just use one scope and repeatedly fork fibers in this scope rather than using multiple nested scopes, which again creates a memory leak.