Fix Python logging memory leak #3050
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 stringstream buffer was never cleared and eventually contained the entire log.
Morlic-fo
added
category:bug
Morlic-fo
added
the
status:cherry-pick for release
There are |
Confusing names are meant to confuse. |
geoffthemedio
added
the
status:merged
Vezzra
removed
the
status:cherry-pick for release
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 stringstream buffer was never cleared and eventually contained the entire log.
Note that this memory leak was recently amplified by malformed logs (see #3049) but already present in older versions. @Vezzra: This should subsequently be cherry-picked into release.
Resolves #3038