Bug 284063

Summary: virtuoso-t going bonkers
Product: [Unmaintained] nepomuk Reporter: Anders Lund <anderslund>
Component: generalAssignee: Sebastian Trueg <sebastian>
Status: RESOLVED DUPLICATE    
Severity: major CC: me, trueg
Priority: NOR    
Version First Reported In: 4.1   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Anders Lund 2011-10-15 09:31:20 UTC 
Version:           4.1 (using KDE 4.7.2) 
OS:                Linux

After much grief, with kde 4.7.2 file indexing appeared to be working againg - until today. Now, virtuoso-t goes bonkers again, sucking CPU cycles and making the desktop unusable by me.

Why isn't that process running niced to lowest possible priority?

Is there a way I can make it that?

It simply goes wrong too often! It should NOT start doing wild indexing just after a session is started, it should never do anything if there is even a small system load!

Logging out, virtuoso-t does not stop, and appearently prevents kde4init to be shut down (nothing else is running), so something must be wrong with the way it runs and is shut down!

Logging back in with a running kde4init leads to a broken kde experience.

Reproducible: Didn't try

Steps to Reproduce:
bko is broken

Actual Results:  
bko is broken

Expected Results:  
bko is broken

OS: Linux (i686) release 3.0-ARCH
Compiler: gcc
Comment 1 Anders Lund 2011-10-15 09:42:28 UTC 
After some 10-15 minutes, cpu usage is down to normal, and I get to use the computer again. Nepomuk is now doing the infinite reindexing of my mail folder, but I think I heard that was fixed, that would be great :)

I think logging in with a left-over virtuoso-t process is very bad btw, sometimes that leads to even more load, and sometimes data appears to dissapear in that situation.
Comment 2 Sebastian Trueg 2011-10-25 14:14:17 UTC 

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