18 Jul
2011
18 Jul
'11
2:02 p.m.
Hendrik Visage <hvjunk@gmail.com> writes:
Hi Gergely,
Looks like I have a syslog-ng 3.3beta1 (fetched from GITHEAD) that is having a serious memory leak (and I'm not yet pushing all our logs to it ;(
Any advice in how to help you track this problem?
Hrm. Well, valgrind would be best, but that slows things down to almost a grounding halt. (But in case you want to try that: G_SLICE=always-malloc valgrind --leak-check=full -v --show-reachable-yes --log-file=valgrind.log syslog-ng -F would be the command to run ;) Other than that, a config could be useful, so I can try and reproduce the problem (or at least identify possible areas where the leak might be coming from, and go from there), and see if I can fix it. -- |8]