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.

Description of problem:
In version 9.11.12-2 new GeoIP was enabled(bug #1564443). When testing reproducer for bug #1578051, it was discovered each reload increments memory usage. Increments are reliable even after 10 reloads.

Version-Release number of selected component (if applicable):
bind-9.11.13-1.el8

How reproducible:
reliable

Steps to Reproduce:
1. systemctl restart named
2. pmap -x $(pidof named) | tail -n1
3. rndc reload
4. pmap -x $(pidof named) | tail -n1
5. rndc reload
6. pmap -x $(pidof named) | tail -n1

Actual results:
Memory usage increments every reload

Expected results:
Memory usage increments on first reload only

Additional info:
For some reason, BIND always increments memory usage on the first reload. That is expected, probably required to keep both old configuration and new during loading. However, pmap shows new mapping after every reload.

Upstream fix for this issue exists, was released in next release after current rebase [1].

1. https://gitlab.isc.org/isc-projects/bind9/commit/95a5589fa2ac3956fecfef780158a2745718c860

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.

https://access.redhat.com/errata/RHSA-2020:1845