https://bugs.kde.org/show_bug.cgi?id=287187
Summary: akonadi_nepomuk_feeder can make Virtuoso eat all my
CPU, when it autosuspends.
Product: Akonadi
Version: 4.8
Platform: Chakra
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Nepomuk Feeder Agents
AssignedTo: [email protected]
ReportedBy: [email protected]
CC: [email protected], [email protected]
Version: 4.8 (using Devel)
OS: Linux
When I have the akonadi_nepomuk_feeder in KDE 4.8 beta 1, Virtuoso eats one of
my cores, and, when akonadi_nepomuk_feeder is doing more than one task at once,
Virtuoso will eat all of my CPU.
Ironically, this happens when akonadi_nepomuk_feeder decides to suspend its
processing, since "the system is busy". If the Nepomuk feeder restarts, nothing
happens and Virtuoso CPU usage won't recede, but a new suspension has the
potential to make Virtuoso eat all of my CPU.
KDE 4.8 Beta 1, packages from kde-unstable, Chakra.
Reproducible: Always
Steps to Reproduce:
1. Boot. akonadi_nepomuk_feeder starts after all agents.
2. Press a key. akonadi_nepomuk_feeder will decide that "system is busy" and it
will stop indexing.
3. Virtuoso CPU usage will skyrocket.
Actual Results:
The CPU usage for Virtuoso goes between 50% and 100%. A strace shows that
Virtuoso spends all that CPU waiting for something, so, it's a waste.
Expected Results:
If Virtuoso isn't doing anything, it should consume no CPU.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
_______________________________________________
Kdepim-bugs mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/kdepim-bugs
