fix: http connection leak in NewBearer() #387
Merged
Conversation
This file contains 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
The `response.Body` for the first `http.Get()` call in `NewBearer()` is not closed. This leaks connections to the `registry` server and can result in substantial memory usage in the `registry`, as the registry allocates a 4MB buffer for each connection and neither end enforces an idle timeout. Fixes enix#378
|
Thanks for your contribution! |
|
🎉 This PR is included in version 1.10.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The
response.Bodyfrom the firsthttp.Get()call inNewBearer()is not closed. This leaks connections to theregistryserver and can result in substantial memory usage, as the registry allocates a 4MB buffer for each connection and neither end enforces an idle timeout.Fixes #378