RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1881852 - Memory leak in python3-dnf
Summary: Memory leak in python3-dnf
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: dnf
Version: 8.2
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: 8.0
Assignee: amatej
QA Contact: Eva Mrakova
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-23 08:38 UTC by Matīss Treinis
Modified: 2021-05-18 15:01 UTC (History)
5 users (show)

Fixed In Version: libdnf-0.55.0-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-18 15:00:36 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Matīss Treinis 2020-09-23 08:38:09 UTC
Description of problem:

python3-dnf use in Python code seems to result in a pretty severe memory leak. Not sure as to what causes this.

Example code:


```
import dnf

for i in range(0, 1000):
    with dnf.Base() as dnf_base:
        dnf_base.fill_sack()
```

Above code results in a steady increase in memory use after about 10-20 cycles, for ~0.5MB/5-10seconds.

Invoking `dnf_base.read_all_repos()` before fill_sack leaks even more - ~5-8MB per cycle depending on the system.

```
with dnf.Base() as dnf_base:
    dnf_base.read_all_repos()
    dnf_base.update_cache()
    dnf_base.fill_sack()
```

Version-Release number of selected component (if applicable):

4.2.17-7.el8_2

How reproducible: pretty reproducible.


Steps to Reproduce:
1. Execute code above
2. Measure memory use of the process


Actual results: memory use increases steadily and indefinitely


Expected results: memory use does not increase.


Additional info: N/A

Comment 2 amatej 2020-10-08 09:51:09 UTC
Thank you for the report, I believe that the memory leaks you mentioned are resolved by PRs:
https://github.com/rpm-software-management/libdnf/pull/984
https://github.com/rpm-software-management/libdnf/pull/1001

In addition I made this small PR:
https://github.com/rpm-software-management/dnf/pull/1671
that should fix few different leaks (reproduced when using security filters, such as --security, and some dnf plugins)

Comment 14 errata-xmlrpc 2021-05-18 15:00:36 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 (dnf bug fix and enhancement update), and where to find the updated
files, follow the link below.

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

https://access.redhat.com/errata/RHBA-2021:1657


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