Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionStuart Auchterlonie
2015-02-25 17:04:48 UTC
Created attachment 995271[details]
Output of /proc/<pid>/smaps for lldpad consuming excess memory
Description of problem:
lldpad memory usage increases over time
Version-Release number of selected component (if applicable):
lldpad-0.9.46-2.el6.x86_64
lldpad-libs-0.9.46-2.el6.x86_64
How reproducible:
100% by customer
Steps to Reproduce:
1. run lldpad for an extended period of time
2.
3.
Actual results:
Memory usage of lldpad increases
Expected results:
Memory usage of lldpad should remain stable over time
Additional info:
See lines 44-46 of smaps data
Comment 1Stuart Auchterlonie
2015-03-02 13:39:48 UTC
One further bit of information from the customer, every server that they
saw this happening on, is actually a VM running on an ESXi hypervisor.
So they shouldn't really be running lldpad on these servers, but equally
lldpad should not leak memory just because it's running on a VM.
I am seeing the same problemm also on a ESXi hypervisors. It appears to be trying to access something that doesn't exist on VMs and loops about once per second trying to access the resource. Every time it loops, it adds about 5 bytes to the memory footprint. These are El6 and El7 hosts.
Several of the subtype modules look to have incorrect return values when encountering unexpected TLVs. It makes it look as if they have taken ownership of an allocation, and if nobody else actually claims it then the memory will be leaked.
I'm working up a test build, will share it when it's ready.
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/RHBA-2019:2339
Created attachment 995271 [details] Output of /proc/<pid>/smaps for lldpad consuming excess memory Description of problem: lldpad memory usage increases over time Version-Release number of selected component (if applicable): lldpad-0.9.46-2.el6.x86_64 lldpad-libs-0.9.46-2.el6.x86_64 How reproducible: 100% by customer Steps to Reproduce: 1. run lldpad for an extended period of time 2. 3. Actual results: Memory usage of lldpad increases Expected results: Memory usage of lldpad should remain stable over time Additional info: See lines 44-46 of smaps data