Version: unspecified (using Devel) OS: Linux nepomukindexer is using 100% time of one cpu core when it tries to index certain pdfs. It looks like it reads the same location in the file again and again. I know, it doesn't crash the application, but it makes using the index service unusable. thx Mich; Reproducible: Always Steps to Reproduce: just run nepomukindexer on the attached file
I don't know if it is related to this bug, but the virtuaoso-t process eats up tons of RAM, although I have specified a limit in the configuration.
I am experiencing similar troubles here. The sad thing is that nepomukindexer starts starting more than one process over time (runs 3 times right now, and if I'm not mistaken it should be one). This problem could be related to https://bugs.kde.org/show_bug.cgi?id=281779 Now, each of those three processes eats 25 % CPU, overall 75 % of my cpu power (2 cores, so 1.5 cores are used now). nepomuk does not seem to react as well, if I disable nepomuk all the things keep running. Anything we can do to trace that?
Me too. This bug makes nepomuk unusable.
*** This bug has been marked as a duplicate of bug 231936 ***