[syslog-ng] 3.3.4 anyone else notice a memory leak

[Gergely Nagy]

Evan Rempel <erempel at uvic.ca> writes:

> OK, I think I can state that there is a memory problem. I would not
> classify it as a leak in that valgrind does not show it, but that just
> means that the original pointer is not lost.

I believe that's what valgrind calls "still reachable".

> I just made a pipe, made syslog-ng read from it and write to a program destination of 'cat > /dev/null'
>
> Then cat a large file (200,000 lines, I used an exisitng syslog file) to the pipe. Watch the memory grow.
> Repeat the process and watch the memory grow more.
> Seems to grow by about 3 MB every time I cat the file.

Mmhm, that should be easy to reproduce. Thanks for the research so far,
I'll look into it soon!

-- 
|8]