Public bug reported: This is noticed during health-check's tests on trusty (mostly i386) ISO's.
The failed builds in https://jenkins.qa.ubuntu.com/view/Trusty/view/Smoke%20Testing/job /trusty-desktop-i386-smoke-health-check/ are all due to this issue. The following is excerpts from cking's debugging of the failure: "NetworkManager does not show this issue when no connections are made old connections are re-established. Only new connections since reboot seem to trigger this. The large mmap is a bit ridiculous, it's either the heap (via malloc/free) or glib memory allocator being a bit generous in the way it requests more memory for the heap or network manager itself doing a large mmap request (which I think is very unlikely). The good news is that the memory is mapped but not all used, so there is little actual physical demand for these mapped in pages. Even so, I think it may be worth somebody with NetworkManager experience to dig in deeper to see why and where this allocation is occurring as a medium/low bug. To reproduce this issue: 1. Clean boot 2. Wait until existing network connections are established (e.g. wifi) 3. Run health-check on Network Manager 4. Make a new connection, e.g. plug in ethernet connection for an auto-ethernet connection to be established. 5. Stop health-check, observe that a huge allocation has occurred." ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu7.1 ProcVersionSignature: Ubuntu 3.19.0-28.30~14.04.1-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic i686 ApportVersion: 2.14.1-0ubuntu3.13 Architecture: i386 Date: Mon Sep 21 13:24:45 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-09-08 (13 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150908) IpRoute: default via 192.168.122.1 dev eth0 proto static 192.168.122.0/24 dev eth0 proto kernel scope link src 192.168.122.148 metric 1 IwConfig: lo no wireless extensions. eth0 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR=<set> LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 1 85b3134d-a657-40be-8229-248bcd0ce79c 802-3-ethernet 1442841756 Mon 21 Sep 2015 01:22:36 PM UTC yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernet connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8 connected enabled enabled enabled enabled disabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty ** Summary changed: - when a new connection occurs, NetworkManager mmaps 64Mb hunk which is equivalent to the 32.28Kb per second rate over a 1800 second (30 minute) run of heath-check + When a new connection occurs, NetworkManager mmaps 64Mb hunk which is equivalent to the 32.28Kb per second rate over a 1800 second run of heath-check ** Description changed: This is noticed during health-check's tests on trusty (mostly i386) ISO's. The failed builds in https://jenkins.qa.ubuntu.com/view/Trusty/view/Smoke%20Testing/job /trusty-desktop-i386-smoke-health-check/ are all due to this issue. - NetworkManager does not show this issue when no connections are made old + + The following is excerpts from cking's debugging of the failure: + + "NetworkManager does not show this issue when no connections are made old connections are re-established. Only new connections since reboot seem to trigger this. + The large mmap is a bit ridiculous, it's either the heap (via + malloc/free) or glib memory allocator being a bit generous in the way it + requests more memory for the heap or network manager itself doing a + large mmap request (which I think is very unlikely). + + The good news is that the memory is mapped but not all used, so there is + little actual physical demand for these mapped in pages. Even so, I + think it may be worth somebody with NetworkManager experience to dig in + deeper to see why and where this allocation is occurring as a medium/low + bug. To reproduce this issue: 1. Clean boot 2. Wait until existing network connections are established (e.g. wifi) 3. Run health-check on Network Manager 4. Make a new connection, e.g. plug in ethernet connection for an auto-ethernet connection to be established. - 5. Stop health-check, observe that a huge allocation has occurred. + 5. Stop health-check, observe that a huge allocation has occurred." ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu7.1 ProcVersionSignature: Ubuntu 3.19.0-28.30~14.04.1-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic i686 ApportVersion: 2.14.1-0ubuntu3.13 Architecture: i386 Date: Mon Sep 21 13:24:45 2015 IfupdownConfig: - # interfaces(5) file used by ifup(8) and ifdown(8) - auto lo - iface lo inet loopback + # interfaces(5) file used by ifup(8) and ifdown(8) + auto lo + iface lo inet loopback InstallationDate: Installed on 2015-09-08 (13 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150908) IpRoute: - default via 192.168.122.1 dev eth0 proto static - 192.168.122.0/24 dev eth0 proto kernel scope link src 192.168.122.148 metric 1 + default via 192.168.122.1 dev eth0 proto static + 192.168.122.0/24 dev eth0 proto kernel scope link src 192.168.122.148 metric 1 IwConfig: - lo no wireless extensions. - - eth0 no wireless extensions. + lo no wireless extensions. + + eth0 no wireless extensions. NetworkManager.state: - [main] - NetworkingEnabled=true - WirelessEnabled=true - WWANEnabled=true - WimaxEnabled=true + [main] + NetworkingEnabled=true + WirelessEnabled=true + WWANEnabled=true + WimaxEnabled=true ProcEnviron: - TERM=screen - PATH=(custom, no user) - XDG_RUNTIME_DIR=<set> - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=screen + PATH=(custom, no user) + XDG_RUNTIME_DIR=<set> + LANG=en_US.UTF-8 + SHELL=/bin/bash RfKill: - + SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: - NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH - Wired connection 1 85b3134d-a657-40be-8229-248bcd0ce79c 802-3-ethernet 1442841756 Mon 21 Sep 2015 01:22:36 PM UTC yes no /org/freedesktop/NetworkManager/Settings/0 + NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH + Wired connection 1 85b3134d-a657-40be-8229-248bcd0ce79c 802-3-ethernet 1442841756 Mon 21 Sep 2015 01:22:36 PM UTC yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: - DEVICE TYPE STATE DBUS-PATH - eth0 802-3-ethernet connected /org/freedesktop/NetworkManager/Devices/0 + DEVICE TYPE STATE DBUS-PATH + eth0 802-3-ethernet connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: - RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN - running 0.9.8.8 connected enabled enabled enabled enabled disabled + RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN + running 0.9.8.8 connected enabled enabled enabled enabled disabled -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1497996 Title: When a new connection occurs, NetworkManager mmaps 64Mb hunk which is equivalent to the 32.28Kb per second rate over a 1800 second run of heath-check To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1497996/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
