Memory Leaks in Nepomuk – Nah!

OK – this is the fifth time I start the first sentence. So now I will just write like it comes to mind… backspace, backspace, mark/delete…. Oh, damn it. I just pushed a fix to master and 4.7 which fixes the memory leak in the filewatch service. The root of it was the same as in the file indexer service: no event loop in the work thread means DBus events piling up without ever being garbage collected.

Well, that is fixed now and the filewatch service will not steal all your memory anymore.

I have three days left until KDE 4.7.3 and I want to make them count!

As always:

Click here to lend your support to: Nepomuk - The semantic desktop on KDE and make a donation at www.pledgie.com !
Click here to donate to Nepomukvia Moneybookers

Advertisement

17 thoughts on “Memory Leaks in Nepomuk – Nah!

  1. Ok, after wining the last time, this time a complete and sincere:

    YOU ROCK

    Sorry for shouting. :) I finally found my way to using the DONATE button, too. Keep going. :)

  2. Great job ! :-)

    Alex

  3. If this is getting into 4.7.3, I will make a Party!

    • It will be in 4.7.3. :)

  4. If only I were to see an analogous fix in akonadi_nepomuk_email_feeder… (this time is dbus-daemon eating a gig of RAM, so, the problem must be similar)

    • Yeap, I have the same.

      • Here too… And that fix should also make it into 4.7.3 so that it makes it into the upcoming openSUSE 12.1 release (in 22 days) :D

    • I suppose there is a bug report, too. Do you have the link (that avoids searching a non-semantic bug database ;)

      • Yes, I saw that, and you told us, in that bug report: the akonadi_nepomuk_email_feeder bug is gone with precisely this bugfix!

        You told us to retest with KDE 4.7.3, so we’ll do that.

      • Maybe, this is the bug :)
        https://bugs.kde.org/show_bug.cgi?id=279800

  5. As you are working on filewatch I had a question about KInotify http://api.kde.org/4.5-api/kdebase-runtime-apidocs/nepomuk/html/classKInotify.html

    Would it be possible to implement rm_watch http://linux.die.net/man/7/inotify ? That would be great.

    Thanks

    • There already is removeWatch. Since Nepomuk does not need more than that I doubt that I will implement any more API. There is more pressing matters for me. :P

      • ok, thanks for your reply

  6. FINALLYYYYYYYYY!!!!!!

  7. +1 Sebastian! Excellent work and I’m going to keep a very close watch on this new release.

  8. Amazing. Thank you!

  9. Pingback: KDE 4.7.3 – The (First) Nepomuk Stability Release | Trueg's Blog

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Connecting to %s