Version:           4.8 (using Devel) 
OS:                Linux

Sometimes, when akonadi_nepomuk_feeder indexes mail, virtuoso-t can be left in a locked up state (100% cpu usage). The lock up can appear randomly, and if it appears, the only way to restore normal funcionality is to stop akonadi (if virtuoso_t is locked up, it will remain using 100% cpu after Akonadi is stopped), kill the locked up copy of virtuoso-t, and restart Akonadi.

Reproducible: Sometimes

Steps to Reproduce:
This happens randomly, but it can be triggered by:

- Adding a mail account.
- Adding the Facebook resource.
- Adding the Google resources.

Actual Results:  
virtuoso_t is left using 100%, no matter what I do. This is complex, since that CPU usage masks the real impact of mail indexing in resources

Expected Results:  
virtuoso_t uses a variable amount of CPU, and, when akonadi_nepomuk finishes, virtuoso_t uses 2% to 3%.

KDE 4.8 RC1.