| Summary: | After performing search across several imap accounts, virtuoso has high cpu and won't stop | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] Akonadi | Reporter: | Martin Tlustos <martin.tlustos> |
| Component: | general | Assignee: | kdepim bugs <pim-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | sven |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | process detail taken from system monitor | ||
|
Description
Martin Tlustos
2013-04-15 12:59:48 UTC
Created attachment 78928 [details]
process detail taken from system monitor
Anything that works with akonadi or nepomuk is blocked: dolphin, kontact, konqueror, akonadi-console. Update: disabling email indexing in nepomuk and force-close virtuoso-t "resolves" the issue. But as soon as I re-enable email indexing in nepomuk, the problem starts again. (In reply to comment #3) > Update: disabling email indexing in nepomuk and force-close virtuoso-t > "resolves" the issue. But as soon as I re-enable email indexing in nepomuk, > the problem starts again. Did you have a search folder in kmail with a very high e-mail count? I had this (over 10,000 "hits") when I messed up an e-mail search. After removing the "Last search" folder, nepomuk went silent. (However, since then nepomuk starts several virtuoso-t instances which use ~50% of my 4GB RAM. No idea why.) Seems resolved with Baloo. Closing. |