Limit high-memory logging ('pattern not matched' in parsing) to necessary log level#4995
Merged
daipom merged 1 commit intofluent:masterfrom Jun 5, 2025
Merged
Conversation
…tched' Signed-off-by: Shizuo Fujita <fujita@clear-code.com>
Contributor
|
Thanks! Note: Long strings are allocated on the heap, so they are likely not released immediately. |
daipom
approved these changes
Jun 5, 2025
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
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.
Which issue(s) this PR fixes:
Fixes #
What this PR does / why we need it:
Currently, the “pattern not matched” warning is always generated regardless of the
log_levelsetting. This warning might use a lot of memory when the log is very long.To reduce memory usage, this PR will generate warnings only when necessary, according to
log_level.Related to #4994
Here is memory usage.

Docs Changes:
Not needed.
Release Note:
Same as the title.