Summary: | filewatch hogging one core gobbling RAM | ||
---|---|---|---|
Product: | [Unmaintained] nepomuk | Reporter: | Blackpaw <lindsay.mathieson> |
Component: | filewatch | Assignee: | Nepomuk Bugs Coordination <nepomuk-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | major | CC: | lindsay.mathieson, me, nepomuk-bugs |
Priority: | NOR | ||
Version First Reported In: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Blackpaw
2013-03-20 11:32:01 UTC
Also the fileindexer was not running after this. Oh!! So the filewatch service is gobbling up all the memory! I thought it was the storage service. Have you been moving a lot of files or something? >Have you been moving a lot of files or something?
Afraid not. And the builds I've been doing are excluded from the watch list
Alright. Please run the file watch service under massif. $ qdbus org.kde.nepomuk.services.nepomukfilewatch /servicecontrol shutdown $ valgrind --tool=massif nepomukservicestub "nepomukfilewatch" I need to see what is consuming all the memory. Ping? Is this still gobbling a lot of your RAM? Ping? Yah, I think we can close this one - not an issue now for me. Thanks. |