Registered Member
|
I've been watching this for some time.
If I ssh in to my computer and run kmail, the nepomuk process on the server side goes crazy and begins to consume huge amounts of memory. At first, I thought if I stopped indexing mail on the server this might solve the problem. But it makes no difference. Simply sshing to the server and starting kmail remotely causes this problem. After doing this last night, I see that as of this morning strigi is constantly re-indexing and the nepomukservices memory use is: 3.6 gb (almost 4 gb for all nepomukservices). |
Administrator
|
Did you have a KDE session running on the remote system?
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
yes I did - the remote computer is a 32bit gentoo; the server a amd64. They have exactly the same kde on them (4.4.3), same akonadi-server (1.3.1), same strigi (0.7.2), same virtuoso- server (6.1.1). |
Administrator
|
Were you logged into KDE on the remote system being accessed?
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
yes I was. But yesterday I logged in from a ubuntu machine and nepomuk on the server again went crazy and began to consume memory. On the other hand, I still see this memory consumption without any remote login as well. For example, right now nepomuk is rapidly growing in memory use (up to 600mb right now). This seemed to be caused by copying a large set of files into my home directory (which is *NOT* indexed by the way, only home/mydocs is indexed). |
Registered Member
|
small addendum to my last message: after logging out and logging
back in to kde, the memory problem persists (nepomuk immediately started consuming memory ...) Plus, I now have (as I do periodically) the dreaded double entry - nepomuk returns *TWO* of every file in a search Sad to say, this software is ****. |
Administrator
|
I would recommend disabling the Strigi file indexing component, which should prevent it from using large quantities of memory. Assuming you do not need to keep your tags, I would also recommend clearing your Nepomuk Database.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered users: Bing [Bot], Evergrowing, Google [Bot], rblackwell