[SSSD] [PATCH] Plug memory leaks in sysdb_ops (Jakub Hrozek)
Jan Zelený
jzeleny at redhat.com
Mon Oct 24 07:07:25 UTC 2011
> Jakub - I figured out why my debug log file was empty. I only had
> debugging enabled for nss and pam!
>
> In any event, yes, I now see the memory leaks. My valgrind summary for
> sssd_be, after running it for a while, is:
>
> ==31457== LEAK SUMMARY:
> ==31457== definitely lost: 128,911 bytes in 1,312 blocks
> ==31457== indirectly lost: 105,416,263 bytes in 899,812 blocks
> ==31457== possibly lost: 3,303,640 bytes in 27,120 blocks
> ==31457== still reachable: 758,871 bytes in 4,324 blocks
> ==31457== suppressed: 0 bytes in 0 blocks
>
> I tried using your patch file, but it couldn't properly patch my version of
> sysdb_ops.c (I was using a compiled version of 1.6.1).
>
> I think what I'll do is to reinstall the REDHAT version of SSSD, disable
> caching, and wait until a properly patched version of SSSD is either
> released from Redhat or the SSSD site. Thanks. - Mark
You can check out current git master if you don't want to wait. Releasing a
new version can take some time (1.7 will take a few weeks). Also it would help
us find out if the issue is really fixed or not.
Jan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <https://lists.fedorahosted.org/pipermail/sssd-devel/attachments/20111024/f4786769/attachment.sig>
More information about the sssd-devel
mailing list