#2170 sssd_nss grows memory footprint when netgroups are requested
Closed: Fixed None Opened 5 years ago by jhrozek.

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


Fields changed

owner: somebody => lslebodn
priority: major => critical

Fields changed

patch: 0 => 1
status: new => assigned

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.11.3

resolution: => fixed
status: assigned => closed

Fields changed

changelog: => The SSSD did not free per-client allocated memory when netgroups were requested. As a consequence, if netgroups were used by a long-running application, the sssd_nss process grew large in memory consumption.

Metadata Update from @jhrozek:
- Issue assigned to lslebodn
- Issue set to the milestone: SSSD 1.11.3

2 years ago

Login to comment on this ticket.

Metadata