Bug 1461643
Summary: | The NetworkManager process continues to consume increasing amounts of memory. | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Robin K I <rki> | ||||
Component: | NetworkManager | Assignee: | Beniamino Galvani <bgalvani> | ||||
Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | high | ||||||
Version: | 7.3 | CC: | aloughla, atragler, bgalvani, bkhoo, fgiudici, lrintel, misalunk, nbhatt, pep, rkhan, rki, sukulkar, thaller, vbenes | ||||
Target Milestone: | rc | ||||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2018-04-10 13:24:24 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 1420851, 1470965 | ||||||
Attachments: |
|
Description
Robin K I
2017-06-15 04:10:04 UTC
Hi, I think this is a different issue than bug 1436650, because that was reported as fixed by other users. Maybe you can try to run NM under valgrind for some time (at least 20 minutes), then kill it with Control-C and attach the log.txt file? Here the steps: yum install valgrind systemctl stop NetworkManager valgrind --leak-check=full /sbin/NetworkManager -d > log.txt 2>&1 # (... kill it after some time) systemctl start NetworkManager Thanks! From the customer case comments I understand that the leak only happens on some machines and not on others. Do you have any idea about the differences in configuration between those? The attached valgrind log doesn't show any evident memory leak. I also tried to reproduce the scenario in a VM where ovs slaves are constantly added and removed, but I see a constant memory usage. Would you mind doing another try with the following commands, which should capture also the memory blocks that are still reachable and will show more information about what NM is doing? systemctl mask NetworkManager systemctl stop NetworkManager valgrind --leak-check=full --show-leak-kinds=all --num-callers=40 /sbin/NetworkManager -d --log-level=TRACE > log.txt 2>&1 # Wait 15 minutes, then terminate with Ctrl-C Thanks! Created attachment 1337231 [details]
[PATCH] bus-manager: don't leak connections
(In reply to Beniamino Galvani from comment #29) > Created attachment 1337231 [details] > [PATCH] bus-manager: don't leak connections lgtm Patch applied to master: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=5b81d403386324f40af6cc23ad3d26682e52a9fa and nm-1-8: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?h=nm-1-8&id=bb4b6be912570dd5fcfd544519b5e6d880f77e1e *** Bug 1496204 has been marked as a duplicate of this bug. *** 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-2018:0778 The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days |