Created attachment 111979 [details] 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.
Quite some time maildir resource and indexing agent used up so much of bandwidth of an BTRFS Dual SSD RAID 1, that I just used while true; do killall akonadi_indexing_agent ; sleep 1; done to make sure indexing agent is done. Maybe your bug report is the cause for that. But OTOH it could be that I just did not wait long enough for indexing agent to complete indexing new mails retrieved via POP3 resource. However it should not hog down the machine for minutes for a few thousands of new mails. Using KDEPIM/Akonadi 17.12.3 on Debian Sid.
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!