Bug #18926

Memory leaks when using OpenSCAP

Added by Ondřej Pražák 8 months ago. Updated 8 months ago.

Status:ClosedSpent time:-
Priority:High
Assigned To:Ondřej Pražák
Category:-
Target version:Foreman - Team Marek backlog
Difficulty: Bugzilla link:1432263
Found in release: Pull request:https://github.com/theforeman/smart_proxy_openscap/pull/47
Triaged:No
Story points-
Velocity based estimate-
Releasesmart_proxy_openscap 0.6.3Release relationshipAuto

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 memory Closed 06/29/2017

Associated revisions

Revision 4adace54
Added by Ondřej Pražák 8 months ago

Fixes #18926 - Destroy openscap objects to release memory

Revision e8751c96
Added by Shlomi Zadok 8 months ago

Merge pull request #47 from xprazak2/memleak

Fixes #18926 - Destroy openscap objects to release memory

History

#1 Updated by Ondřej Pražák 8 months ago

  • Subject changed from Memory leaks when using OpenSCAP to Memory leaks when using OpenSCAP
  • Target version set to Team Marek backlog

#2 Updated by The Foreman Bot 8 months ago

  • Status changed from New to Ready For Testing
  • Assigned To 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 8 months ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#4 Updated by Marek Hulán 8 months ago

  • Release set to smart_proxy_openscap 0.6.3

#5 Updated by Ondřej Pražák 5 months ago

  • Related to Bug #20164: smart_proxy_openscap leaks memory added

Also available in: Atom PDF