FS#11465 - Memory leak in NetworkManager
Attached to Project:
Arch Linux
Opened by Victor Temistocles Nardes (vtn) - Saturday, 13 September 2008, 04:08 GMT
Last edited by Jan de Groot (JGC) - Saturday, 07 February 2009, 20:17 GMT
Opened by Victor Temistocles Nardes (vtn) - Saturday, 13 September 2008, 04:08 GMT
Last edited by Jan de Groot (JGC) - Saturday, 07 February 2009, 20:17 GMT
|
Details
Description:
Hello, I am using NetworkManager 0.6.6 (adapter is a Intel Pro Wireless 3945 working with iwl3945) and noticed that its memory usage rises to a huge amount of RAM after some time of wireless connection activity, like 400MB after some hours. Then the connection begins drop or get unstable. I checked the web and found these two references with correction patches: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=488604 http://bugs.gentoo.org/show_bug.cgi?id=234945 I have made changes to PKGBUILD downloaded from the ABS tree, tried the patch and the memory leak was gone. Attached you will find the following files: - NetworkManager-01.png: Screenshot of memory usage when I began working on this problem. - NetworkManager-02.png: Screenshot of memory usage one hour later. - fix-memleak.patch: Patch used. - PKGBUILD: New version of the NetworkManager build script. It seems like Networkmanager reorganized their trunk and there is not the patched file anymore, so it may be solved upstream. Nonetheless, this bug causes such a big problem with NM and is so easy to do a temporary fix that I though it was worth to report it. * package version(s) NetworkManager * config and/or log files etc. networkmanager-0.6.6-1 Steps to reproduce: - Run NetworkManager. - Check its memory usage. - Use it to connect to a wireless connection. - Begin surfing the web, downloading a torrent, etc. - After one hour or so, check its memory usage. |
This task depends upon
Closed by Jan de Groot (JGC)
Saturday, 07 February 2009, 20:17 GMT
Reason for closing: Fixed
Additional comments about closing: Assuming fixed in 0.7.
Saturday, 07 February 2009, 20:17 GMT
Reason for closing: Fixed
Additional comments about closing: Assuming fixed in 0.7.
I believe that this is happening because you're torrenting (or at least, I assume so, because you have KTorrent on).
When you torrent, you create a lot a connections to other networks or computers, and there's generally a massive amount of data throughput (maybe explaining the memory usage). Some routers (I know mine, Linksys something something) store old connections and slow things down after a while - so that may be a factor.
I'm not sure, but this is my best guess about it.
See if you can reproduce this when you're not torrenting.
In the first screenshot, Ktorrent is off.
In the second, it's on, and your mem usage is through the roof.
Possible correlation?