stream: destroy source when map iterator closes early#64264
Open
Y1D7NG wants to merge 1 commit into
Open
Conversation
Fixes: nodejs#64261 Signed-off-by: y1d7ng <y1d7ng@yeah.net>
Collaborator
|
Review requested:
|
nodejs-github-bot
added
needs-ci
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.
Fixes: #64261
When some(), every(), or find() returns early, the underlying map() iterator closes but the source stream is never destroyed, leaving it open and preventing cleanup. The fix calls destroyImpl.destroyer(stream, null) in the map() iterator cleanup path so the source stream is destroyed when the iterator closes early.