Summary: | Huge memleak in nepomuk | ||
---|---|---|---|
Product: | nepomuk | Reporter: | jeanpaul145 |
Component: | general | Assignee: | Sebastian Trueg <sebastian> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | antonio.petrelli, szymon, trueg |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | Image showing the mem usage of the nepomukservices process |
Description
jeanpaul145
2010-04-25 20:18:53 UTC
Created attachment 43028 [details]
Image showing the mem usage of the nepomukservices process
If there's anything else I can do, please let me know. In the mean time I'm turning the Nepomuk system off. 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! I can confirm that behaviour on my system. Currently nepomuk consumes 900MiB while doing initial indexing. *** This bug has been marked as a duplicate of bug 226676 *** |