Version: 4.1 (using Devel) OS: Linux When nepomuk is not activated dbus-daemon memory consumption stays at around 2-3MB of reserved memory. As nepomuk is activated, memory consumption rises consistently. After one hour, dbus-daemon takes 150MB. After a day of work, my laptops becomes unusable and dbus-daemon takes 1.6GB of reserved memory. Killing virtuoso-t process doesn't free this memory from dbus. Virtuoso 6.1.3-1 Shared-desktop-ontologies 0.7.1-1 DBus dbus 1.4.12-1 Kde 4.7 rc2 Kernel 3.0-rc6 x86_64 Reproducible: Always Steps to Reproduce: Activate nepomuk Wait while watching how dbus-daemon memory consumption rises Actual Results: Unacceptable memory consumption of dbus-daemon Expected Results: dbus-daemon shouldn't rise it's memory consumption
Same here after upgrading to KDE 4.7.0 and activating Nepomuk (it's currently using 142MB!).
AFAIK this is fixed. I reported a nepomukstorage memory leak, but Sebastian Trüg supposedly killed this with commit 579935ee7518b06851356d606232d2394c3315b8. In my system, nepomukstorage and Virtuoso memory usage are exploding, but dbus-daemon remains slim.
Fixed indeed. After a reindexing and the pain of suffering another memory leak, memory consumptions are as follows. 249868 K nepomukservicestub nepomukstorage (!!!!) 1265352 K virtuoso-t (1.2 GB!!!!!) 5152 K dbus-daemon 1184 K dbus-daemon So, yes, there is a MASSIVE memory leak, but, with KDE 4.7, it's somewhere else. I filed a bug against nepomukstorage (bug 278591), but dbus-daemon memory usage remains slim here.
See bug 278591. Even that bug disappeared with KDE components packaged properly, Contact your distributor and ask them for: Raptor 2.0.4 Soprano 2.6.52 compiled against Raptor 2.0.4 Rasqal 0.9.26 Redland 1.0.14 Strigi 0.7.5 After that, ensure yourself you have the kde-runtime 4.7.0 respinned (Fedora: kdebase-runtime-4.7.0-3.fc16 or greater, other distros may vary). With those packages, you shouldn't have any dbus-related leaks or problems.
I can confirm this bug with KDE 4.7.0 on Fedora FC15, as well. Re-activated nepomuk last night, result: - virtuoso-t has been churning steadily at 30-50% CPU load (on dual core, so I suspect it's pretty much sucking up one core completely); - dbus-daemon process now is using 1.3 GB of RAM, of which 768K are shared. How can I help narrowing it down?
How sweet: This is indeed just packaging now. http://repos.fedorapeople.org/repos/rdieter/kde47/ still has the bugs, but otherwise the packages seem good. If complemented with the KDE 4.7 packages from rawhide (exception: kde-settings-kdm, which should be the version from FC15) plus strigi, the result looks very good so far. All the memory leak issues seem gone, so I can finally go about seeing what Nepomuk can actually do for me. :) Thanks!
I see that you are using Fedora. That's great, because I'm now seeing this... with akonadi_nepomuk_email_feeder. I just wish that all the bugfixing that happened in Strigi touches also akonadi_nepomuk_email_feeder. To reproduce. 1. Create again the Nepomuk database. a) Disable the Nepomuk system. b) rm -fr ~/.kde/share/apps/nepomuk/repository c) Enable the Nepomuk system. 2. Strigi will index everything. dbus-daemon memory usage will be low (not more than ~10 MB). 3. Type akonadiconsole, restart the Akonadi Nepomuk E-Mail Feeder resource. 4. Let akonadi_nepomuk_email_feeder work. If you have a nicely sized inbox, you'll see dbus-daemon memory usage skyrocket to the stars (361 MB here, and counting) This will only happen once, though, as akonadi_nepomuk_email_feeder doesn't reindex already indexed mails. All this with KDE 4.7.0 + kde-runtime, kde-workspace, kdepim-runtime and kdepim compiled from the stable KDE 4.7.x branch.
I can still reproduce it in Arch and kde 4.7.1 raptor 2.0.4-1 soprano 2.7.0-1 rasqal 1:0.9.27-1 redland 1:1.0.14-1 strigi 0.7.5-4 dbus 1.4.14-1 kdelibs 4.7.1-2
Please test with KDE 4.7.3 at the end of the week. It should have been fixed along with bug 226676.
I've tried to reproduce it again and it seems to work well now.