Bug 1755044 - Memory leak CRIO due to no garbage collection in /run/crio/exits for exited containers
Summary: Memory leak CRIO due to no garbage collection in /run/crio/exits for exited ...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Containers
Version: 4.1.z
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.2.0
Assignee: Mrunal Patel
QA Contact: Sunil Choudhary
Depends On:
Blocks: 1186913 1755584
TreeView+ depends on / blocked
Reported: 2019-09-24 15:34 UTC by David Hernández Fernández
Modified: 2019-10-16 06:42 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1755584 (view as bug list)
Last Closed: 2019-10-16 06:41:50 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github cri-o cri-o pull 2854 0 None closed [1.14] sandbox_remove: Ensure that the pod infra container exit file is removed 2020-05-06 12:45:53 UTC
Red Hat Bugzilla 1730281 0 urgent CLOSED podman leaks kernel memory due to return code stored in tmpfs 2023-09-14 09:37:44 UTC
Red Hat Product Errata RHBA-2019:2922 0 None None None 2019-10-16 06:42:07 UTC

Comment 2 Micah Abbott 2019-09-24 15:56:18 UTC
Sending over to the Containers team for triage

Comment 3 Mrunal Patel 2019-09-24 21:25:19 UTC

Comment 4 Mrunal Patel 2019-09-25 03:07:46 UTC
CRI-O with commit 0d4a9065 should have the fix.

Comment 6 errata-xmlrpc 2019-10-16 06:41:50 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.