Bug 1320183 - NetworkManager slow memory leak
Summary: NetworkManager slow memory leak
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 23
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-22 14:17 UTC by Jason Merrill
Modified: 2017-10-25 17:34 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-07 17:00:03 UTC
Type: Bug


Attachments (Terms of Use)

Description Jason Merrill 2016-03-22 14:17:13 UTC
Description of problem:

The memory use of NetworkManager gradually grows when left running: currently it's been running for just over a week, and is up to 1.5GB virtual, 564MB resident.  When I restart it, memory consumption drops back to 541MB virtual, 15MB resident.

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

NetworkManager-1.0.10-3.fc23.x86_64
NetworkManager-wifi-1.0.10-3.fc23.x86_64
NetworkManager-openvpn-1.0.8-2.fc23.x86_64

How reproducible:

Consistently

Steps to Reproduce:
1. Boot
2. Connect to WiFi and VPN
3. Wait

Actual results:

Increasing memory use

Expected results:

Stable memory use

Additional info:

Comment 1 Blueowl 2016-09-13 15:51:45 UTC
Do you still experience the issue?
If so, could you run NetworkManager in valgrind?

systemctl mask NetworkManager
systemctl stop NetworkManager
valgrind --leak-check=full NetworkManager --debug

Comment 2 Lubomir Rintel 2016-11-07 17:00:03 UTC
I'm wondering if you could update to a more recent NetworkManager? We've fixed a couple of leaks before -- nothing as severe as you're indicating comes to my mind, but still.

Picking NetworkManager from a newer distro should work just fine:

  # dnf --releasever=25 update NetworkManager

Also, please describe you configuration -- what type of the connections do you have, how many devices, etc. Output of the following would be nice:

  # nmcli c
  # nmcli d
  # ip addr
  # ip route
  # ip -6 addr
  # ip -6 route

Please reopen the bug when you're responding with more information.

Comment 3 Jason Merrill 2017-10-25 17:34:03 UTC
Sorry for not responding before; in any case, I'm not seeing this problem in F26.


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