https://bugs.kde.org/show_bug.cgi?id=393067
Bug ID: 393067
Summary: Infinite loop of ItemFetch/ItemModify jobs
Product: Akonadi
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: kdepim-bugs@kde.org
Reporter: tomastr...@gmx.com
Target Milestone: ---
Created attachment 111979
--> https://bugs.kde.org/attachment.cgi?id=111979&action=edit
akonadiconsole log of the problem
I'm running kdepim/akonadi 17.12.3 (Fedora 27) and once in a while, the Akonadi
stack falls into an infinite loop and keeps hogging my CPU until killed. I have
done some poking-around with GDB and akonadiconsole and came up with the
following scenario:
1) The akonadi_maildir_resource services a fetch job
2) ResourceBase::itemsRetrieved processes the fetched item (including the
payload) and immediately triggers an ItemModifyJob on it
(agentbase/resourcebase.cpp:1393)
3) Server::Store::parseStream() is handles the ItemModify job and because
cmd.modifiedParts() contains Protocol::ModifyItemsCommand::Parts, triggers an
update, bumping the item's revision and mtime
4) A change notification is delivered to akonadi_indexing_agent, which in turn
requests retrieval of the modified item from the resource, closing the loop
The end result is a stream of updates that keeps rapidly increasing the
revision of the one affected item (see attached log).
I'm obviously missing something here, and that is where the loop normally gets
broken. Any advice on that or suggestions how to debug this further are very
welcome.
--
You are receiving this mail because:
You are the assignee for the bug.
