Fix postFormAsync memory leak - #135
Closed
ahinkka wants to merge 2 commits into
Closed
Conversation
ahinkka
force-pushed
the
fix/post-form-async-memory-leak
branch
from
August 14, 2026 13:28
eae0c84 to
f189312
Compare
Issue nodejs/node#63574 has already been fixed, but hasn't been released. This bypasses the issue.
Author
|
Closing. Changes are not compatible with browser. |
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
1 participant
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.
This fixes the issue caused by nodejs/node#63574.
The changes made in this PR should be revisited once Node ships a fix to the leak.