Bug 274895 - nepomukindexer hangs on certain pdfs
Summary: nepomukindexer hangs on certain pdfs
Status: RESOLVED DUPLICATE of bug 231936
Alias: None
Product: nepomuk
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Sebastian Trueg
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-04 11:24 UTC by Michi
Modified: 2011-10-06 07:09 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Michi 2011-06-04 11:24:55 UTC 
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
Comment 1 Michi 2011-06-04 11:26:16 UTC 
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.
Comment 2 Georg Grabler 2011-09-13 19:59:00 UTC 
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?
Comment 3 hamelg 2011-10-05 19:46:37 UTC 
Me too.
This bug makes nepomuk unusable.
Comment 4 Sebastian Trueg 2011-10-06 07:09:19 UTC 

*** This bug has been marked as a duplicate of bug 231936 ***