Bug 258039

Summary: Virtuoso-t frying my processor
Product: nepomuk Reporter: Edney Matias <edneymatias>
Component: generalAssignee: Sebastian Trueg <sebastian>
Status: RESOLVED DUPLICATE    
Severity: normal CC: aspotashev, bero, trueg, woskimi
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: Virtuoso-t process after resuming from suspend
...one hour later.

Description Edney Matias 2010-11-27 03:21:23 UTC
Created attachment 53779 [details]
Virtuoso-t process after resuming from suspend

Version:           unspecified (using KDE 4.5.80) 
OS:                Linux

Virtuoso-t is frying my processor every time i do a search on dolphin, open kmail, log in on my desktop or resume from suspend state. It stays on top of my process list for a long time, sometimes i have to stop nepomuk service. I'm reporting against 4.6 beta 1 but it also used to happen on earlier versions. On 4.5.x i had the virtuosoctl to start and stop virtuoso service, but there's no such command on 4.6 beta 1. I'm attaching two screen capture of my process list, one after resuming from suspend and the other one hour later.

I don' t know what else i should include but i can manage it if someone point me out.

Thank you.

Reproducible: Always

Steps to Reproduce:
 1. log in; or
 2. open kmail version 4.5.80; or
 3. do a search on dolphin; or
 4. resume from a suspend state;

Actual Results:  
My CPU fries, a lot o heat on my legs, extra fan noise, a lot of power consumption. 

Expected Results:  
Lower CPU usage.

Anything you need i can check.
Comment 1 Edney Matias 2010-11-27 03:23:03 UTC
Created attachment 53780 [details]
...one hour later.
Comment 2 Michi 2010-11-29 08:12:01 UTC
I can confirm this behaviour especially after resuming from suspend. Sending an INT signal helps however.
Comment 3 Bernhard Rosenkraenzer 2010-12-14 20:08:29 UTC
Duplicate of bug 246678?
Comment 4 Sebastian Trueg 2011-01-05 16:39:12 UTC

*** This bug has been marked as a duplicate of bug 246678 ***
Comment 5 Edney Matias 2011-01-05 17:13:59 UTC
Hi!

Writing to let you know that this behavior still present on 4.6 RC1 and KDEPIM 4.6 beta3.

Best regards.