Description of problem: There must be a serious memory leak since this daemon currently occupies 800MB on my system. I'm running on my system lvm2 test thus a lot of devices are appearing and disappearing during test suite run. VMSIZE: 1058300 kb RSS: 819528 kb total 4 kb shared 0 kb private clean 819524 kb private dirty PRIVATE MAPPINGS vmsize rss clean rss dirty file 816128 kb 0 kb 816080 kb [heap] 2964 kb 0 kb 2964 kb 48 kb 0 kb 48 kb 32 kb 0 kb 32 kb /usr/lib64/libstdc++.so.6.0.17 32 kb 0 kb 32 kb /usr/lib64/libxml2.so.2.7.8 24 kb 0 kb 24 kb /usr/lib64/libudisks2.so.0.0.0 136 kb 0 kb 24 kb [stack] 20 kb 0 kb 20 kb 84 kb 0 kb 16 kb 16 kb 0 kb 16 kb /usr/lib64/libc-2.15.so 16 kb 0 kb 16 kb /usr/lib64/libgio-2.0.so.0.3116.0 8192 kb 0 kb 12 kb ... Version-Release number of selected component (if applicable): gvfs-1.11.3-1.fc17.x86_64 How reproducible: Steps to Reproduce: 1. probably running lvm2 test suite a few times 2. 3. Actual results: Expected results: Additional info:
Sure, could be there's a memory leak, not entirely impossible (I check for memory leaks from time to time while stressing the kernel block subsystem but it's been a while...). Can you also check if the udisksd process is leaking as well? Thanks
So far I'm only killing gvfs-udisks2-volume-monitor as it easily get to 1GB memory size after few runs of lvm test suite. Other daemons in my system do not seem to grow (at least not in such marginal way)
You guys are lightweights. I've got this thing over 5GB ... 1912 rjones 20 0 5042m 4.3g 3248 S 0.0 56.8 3:02.17 gvfs-udisks2-vo Very easy to reproduce too: just run some tests that continually mount and unmount a filesystem.
udisksd is not using a large amount of memory. It's definitely a leak in gvfs-udisks2-volume-monitor alone.
Yeah, sorry, I forgot about this... I'll start working on fixing it. Thanks!
OK, I've fixed the memory leaks with this upstream commit http://git.gnome.org/browse/gvfs/commit/?id=d870015bff4eb8f34f465f4c45d91ca326f52a43 This should be included in F17.
gvfs-1.12.2-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/gvfs-1.12.2-1.fc17
Package gvfs-1.12.2-1.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing gvfs-1.12.2-1.fc17' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-6873/gvfs-1.12.2-1.fc17 then log in and leave karma (feedback).
I can confirm, I'm no longer seeing this leak during my tests
gvfs-1.12.2-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.