Bug 235377 - Huge memleak in nepomuk
Summary: Huge memleak in nepomuk
Status: RESOLVED DUPLICATE of bug 226676
Alias: None
Product: nepomuk
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Sebastian Trueg
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-25 20:18 UTC by jeanpaul145
Modified: 2011-01-06 20:15 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Image showing the mem usage of the nepomukservices process (154.84 KB, image/png)
2010-04-25 20:25 UTC, jeanpaul145
Details

Note You need to log in before you can comment on or make changes to this bug.
Description jeanpaul145 2010-04-25 20:18:53 UTC
Version:            (using KDE 4.4.2)
OS:                Linux
Installed from:    Ubuntu Packages

The process nepomukservices eats a lot more memory than it should.

j@Brutus:~/$ uptime
 20:12:38 up  4:25,  1 user,  load average: 0.37, 0.48, 0.54

With this uptime, nepomukservices has gotten hold of about 1.1 GB of RAM and this number only keeps getting bigger. I know this because yesterday after I installed the RC of Kubuntu Lucid (the AMD64 variety) it ate almost 2 GB, which is half my total amount of RAM.

Obviously, reproduction should be easy - just let your computer sit idle for a while (or do something useful in the meantime - it doesn't really matter for this bug).
Comment 1 jeanpaul145 2010-04-25 20:25:07 UTC
Created attachment 43028 [details]
Image showing the mem usage of the nepomukservices process
Comment 2 jeanpaul145 2010-04-25 20:30:30 UTC
If there's anything else I can do, please let me know. In the mean time I'm turning the Nepomuk system off.
Comment 3 jeanpaul145 2010-05-06 17:40:49 UTC
I noticed something interesting that might help: right now all of Nepomuk uses about 44M of memory, and it is just idly sitting there. This leads me to believe that the bug in question appears only when doing initial indexing (or at least when it has a lot of indexing to do). Hope this helps!
Comment 4 Szymon Janc 2010-05-08 20:02:08 UTC
I can confirm that behaviour on my system.
Currently nepomuk consumes 900MiB while doing initial indexing.
Comment 5 Sebastian Trueg 2011-01-06 20:15:23 UTC

*** This bug has been marked as a duplicate of bug 226676 ***