Skip to content
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.

Sign up for GitHub

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

Jump to bottom

User Defined Types - Memory Leak #223

Open
Amorik opened this issue Nov 1, 2016 · 2 comments · May be fixed by #343
Open

User Defined Types - Memory Leak #223

Amorik opened this issue Nov 1, 2016 · 2 comments · May be fixed by #343
Labels
bug

Comments

@Amorik
Copy link

Amorik commented Nov 1, 2016

Use of User Defined Types (UDT) causes memory leak to occur. Appears to be any form of UDTs though may be more noticeable under higher loads. For configuration examples, valgrind output, or more information see rsyslog-users discussion: http://rsyslog-users.1305293.n2.nabble.com/Liblognorm-User-Defined-Types-Memory-Leak-td7591408.html

~Regards
@rgerhards
Copy link
Member

I have played a bit with it, I hope I can reproduce. If so, this seems to be related to cases where the usser defined type is called, but does not match. Need to see if I can craft more tests.

@rgerhards
Copy link
Member

Unfortunately, I could not reproduce what I had originally seen. So back to begin... Still working on this as time permits.

@Amorik Amorik added the bug label Nov 7, 2016
@ChristophZirnsak ChristophZirnsak mentioned this issue Jul 31, 2019
Open
@ontholerian ontholerian linked a pull request Oct 8, 2020 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fixed a memory leak when a user-defined type has an unparsed result ontholerian/liblognorm
2 participants
@rgerhards @Amorik