[syslog-ng] [Bug 257] memory leak on reload

bugzilla at bugzilla.balabit.com bugzilla at bugzilla.balabit.com
Sat Nov 2 18:40:37 CET 2013


https://bugzilla.balabit.com/show_bug.cgi?id=257





--- Comment #7 from Gergely Nagy <algernon at balabit.hu>  2013-11-02 18:40:37 ---
(In reply to comment #6)
> Created an attachment (id=85)
 --> (https://bugzilla.balabit.com/attachment.cgi?id=85) [details]
> valgrind --leak-check=full --show-reachable=yes --verbose
> 
> here is the
> valgrind --leak-check=full --show-reachable=yes --verbose
> 
> on a syslog-ng compiled with -ggdb3 -O3
> 

Hrm. How many reloads was this? Valgrind only reports about 16-17k leaked memory which isn't all that much... though... syslog-ng is using the slice allocator,
which tends to confuse valgrind at times. I'm sorry I forgot this earlier, but would it be possible to re-run the test with G_SLICE=always-malloc set in the
environment too? And the more reloads the better.


-- 
Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.


More information about the syslog-ng mailing list