[syslog-ng] Possible memleak in 3.3 HEAD

[Gergely Nagy]

Jakub Jankowski <shasta at toxcorp.com> writes:

> It looks like 3.2.2 does not exhibit the leak I'm seeing on 3.3. Complete 
> valgrind logs are available here: http://toxcorp.com/stuff/syslog-ng-leak/
>
> Let me know if I can provide anything else to help with this. Thanks!

Quick update: I managed to reproduce the problem, and I can verify that
this is present in current git head indeed.

I used the following config:

,----
| @version: 3.3
| @include "scl.conf"
| 
| options {
| 	time-reap(1);
| 	create-dirs(yes);
| 	frac-digits(4);
| };
| source s_network {
| 	tcp(port (13514) tags("tcp-tag") flags(no-parse));
| };
| destination d_file {
| 	file("/tmp/many-file/${FIRST:-default}-seq-${UNIXTIME}.log"
| 		template("${REST}\n")
| 	);
| };
| log {
| 	source(s_network);
| 	destination(d_file);
| };
`----

Then do the following: for f in $(seq 1 10000); do echo "host-$f message $f" | nc localhost 13514; done

I have an idea where to look further, will see how far I get.

-- 
|8]