-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Filter plugin memory leak with latest master build #3197
Comments
JeffLuoo
changed the title
Memory Leak: latest master build
Filter plugin memory leak with latest master build
Mar 9, 2021
I also reproduce it. Note: In contrast, this configuration is not leaked.
|
@nokute78 Thank you for the reply! |
edsiper
added a commit
that referenced
this issue
Mar 15, 2021
Signed-off-by: Eduardo Silva <[email protected]>
Thanks. It was a leak when the plugin failed to initialize due to a wrong matching rule, just fixed in e312ef1 |
Thanks for the fix. |
DrewZhang13
pushed a commit
to DrewZhang13/fluent-bit
that referenced
this issue
May 3, 2021
…3197) Signed-off-by: Eduardo Silva <[email protected]>
DrewZhang13
pushed a commit
to DrewZhang13/fluent-bit
that referenced
this issue
May 3, 2021
…3197) Signed-off-by: Eduardo Silva <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
A memory leak is detected when tested with valgrind.
Describe the solution you'd like
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: