NetworkManager increases CPU usage the longer it is run

I have a laptop, but I primarily use an ethernet connection and not wireless. I've noticed that the NetworkManager process sometimes (not all the time, and not consistently) likes to use 20-50% of my CPU time as well. To illustrate this, a screenshot is attached: notice that NetworkManager has used up more time, cumulatively, than any other process on the system.

Hi Matthew
Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with development branch of Ubuntu, Hardy Heron?

Thanks in advance.

It is not an issue for me because I uninstalled NetworkManager and went back to my custom ifup/ifdown scripts.

This problem exists in Gutsy.

I cannot try Hardy, because the installer currently kernel panics on my testing machine. Note that this may be the result of a bad CD - I haven't had time to dig into it any more than to note that it dies.

Hi Matthew
i don't really experience this issue, and would very much appreciate if you can give us your feedback when you finally try Hardy Heron.

Thanks

Will do.

This appears to be fixed in Hardy. I have a machine which has been up for over a week without this problem recurring.

I'm running Hardy and seem to have this very problem -- in the course of a few days, Network Manager CPU usage on my laptop can climb up to 30%. 10% after 24h of uptime is not unusual. Disabling networking and re-enabling it brings CPU usage back to <0.1%.

Currently 20-25% CPU usage, 12h after last restart of NetworkManager. I'm on a wired network (dhcp) with wireless disabled.

network-manager 0.6.6-0ubuntu5

I can't see anything related in any of the logs in /var/log.

This bug is possibly related to:

https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/162383

So I've killed NetworkManager and started it manually with the --no-daemon option. Here's the immediate output:

NetworkManager: <info> starting...
NetworkManager: <info> New VPN service 'ppp' (org.freedesktop.NetworkManager.ppp_starter).
NetworkManager: <info> Found radio killswitch /org/freedesktop/Hal/devices/ipw_wlan_switch
NetworkManager: <info> eth1: Device is fully-supported using driver 'ipw2200'.
NetworkManager: <info> eth1: driver supports SSID scans (scan_capa 0x21).
NetworkManager: <info> nm_device_init(): waiting for device's worker thread to start
NetworkManager: <info> nm_device_init(): device's worker thread started, continuing.
NetworkManager: <info> Now managing wireless (802.11) device 'eth1'.
NetworkManager: <info> Deactivating device eth1.
NetworkManager: <info> eth0: Device is fully-supported using driver 'skge'.
NetworkManager: <info> nm_device_init(): waiting for device's worker thread to start
NetworkManager: <info> nm_device_init(): device's worker thread started, continuing.
NetworkManager: <info> Now managing wired Ethernet (802.3) device 'eth0'.
NetworkManager: <info> Deactivating device eth0.
NetworkManager: <info> Updating allowed wireless network lists.
NetworkManager: <info> Updating VPN Connections...
NetworkManager: <info> Wireless now enabled by radio killswitch
NetworkManager: <info> Will activate wired connection 'eth0' because it now has a link.
NetworkManager: <info> SWITCH: no current connection, found better connection 'eth0'.
NetworkManager: <info> Will activate connection 'eth0'.
NetworkManager: <info> Device eth0 activation scheduled...
NetworkManager: <info> Activation (eth0) started...
NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful.
NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
NetworkManager: <info> Activation (eth0) Beginning DHCP transaction.
NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
NetworkManager: <info> DHCP daemon state is now 12 (successfully started) for interface eth0
NetworkManager: <info> DHCP daemon state is now 1 (starting) for interface eth0
NetworkManager: <info> DHCP daemon state is now 2 (bound) for interface eth0
NetworkManager: <i...

We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

This no longer appears to be an issue in Intrepid.

Thanks you Matthew. This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status . Thank you again for taking the time to report this bug and helping to make Ubuntu better. Feel free to submit any future bugs you may find.