Cause: Memory was not freed corectly
Consequence: Memory growth if the application requesting netgroups was a long-running one
Fix: Memory is freed corectly
Result: Memory is no longer leaking even in long-running applications
The valgrind error was not related after all. We found out that we didn't free a memory context where we should, which resulted in memory growth if the application requesting netgroups was a long-running one.
To reproduce:
1) Run a process that requests a netgroup periodically but doesn't exit between the attempts. Maybe a deamon, python interpreter might do as well.
2) Watch the sssd_nss memory footprint grow
Created attachment 832692[details]
source code of reproducer
Bug can be reproduced with attached example program.
gcc -Wall netgroup.c -o netgroup
./netgroup netgroup_name
Memory leak is reproducible also with non-existing netgroup.
RSS of sssd_nss process was increased about 200 MB in 3 minutes.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2014-1375.html