Project

General

Profile

Bug #18926

Memory leaks when using OpenSCAP

Added by Ondřej Pražák about 6 years ago. Updated almost 5 years ago.

Status:
Closed
Priority:
High
Difficulty:
Triaged:
No
Bugzilla link:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

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

Related to OpenSCAP - Bug #20164: smart_proxy_openscap leaks memoryClosed2017-06-29

Associated revisions

Revision 4adace54 (diff)
Added by Ondřej Pražák about 6 years ago

Fixes #18926 - Destroy openscap objects to release memory

Revision e8751c96
Added by Shlomi Zadok about 6 years ago

Merge pull request #47 from xprazak2/memleak

Fixes #18926 - Destroy openscap objects to release memory

History

#1 Updated by Ondřej Pražák about 6 years ago

  • 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

  • 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

#4 Updated by Marek Hulán about 6 years ago

  • 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

Also available in: Atom PDF