Bug #18926
Memory leaks when using OpenSCAP
Difficulty:
Triaged:
No
Bugzilla link:
Description
Description of problem:
A user is noticing that foreman-proxy is dying and we suspected it was due to the large amount of clients being checked by the OpenSCAP plugin. I tried to reproduce locally and saw the same issue.
How reproducible:
100%
Steps to Reproduce:
1. Set up a system with one host, an OpenSCAP policy and attach the policy to the host.
2. Set OpenSCAP to scan the host every minute
Actual results:
Memory usage balloons until the OOM killer terminates foreman-proxy
Expected results:
Memory usage remains relatively constant.
Related issues
Associated revisions
History
#1
Updated by Ondřej Pražák about 6 years ago
Updated by - Subject changed from Memory leaks when using OpenSCAP to Memory leaks when using OpenSCAP
- Target version set to 115
#2
Updated by The Foreman Bot about 6 years ago
Updated by - Status changed from New to Ready For Testing
- Assignee set to Ondřej Pražák
- Pull request https://github.com/theforeman/smart_proxy_openscap/pull/47 added
#3
Updated by Ondřej Pražák about 6 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset smart_proxy_openscap|4adace544b37790456451e316d2a71387708d1ab.
#4
Updated by Marek Hulán about 6 years ago
Updated by - Legacy Backlogs Release (now unused) set to 232
#5
Updated by Ondřej Pražák almost 6 years ago
- Related to Bug #20164: smart_proxy_openscap leaks memory added
Fixes #18926 - Destroy openscap objects to release memory