Comment 18 for bug 578215

Revision history for this message
Mark Greenwood (fatgerman) wrote :

I've got this problem on Maverick, with KDE 4.5.3. With file indexing enabled virtuoso-t keeps the CPU at 99% indefinitely *even* if I then disable file indexing again. I have to reboot after disabling indexing.
Also, if I enable the option in digikam to store metadata in nepomuk, the same thing happens.
However I've found that if increase the memory available to nepomuk (from System Settings) this problem goes away. I have, however, had to allow it to use 400MB of RAM, which is way unacceptable.
I think, if you only index a very small number of files the default amount of memory is probably fine, but I now have 18,000 files in my database (it has indexed all my MP3s and Photos, which is what I wanted it to do).