Bug 346611 - Akonadi Notes Agent hoggs all computer resources
Summary: Akonadi Notes Agent hoggs all computer resources
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: akonadiconsole (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR grave
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-04-25 01:48 UTC by uli
Modified: 2018-02-01 09:51 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description uli 2015-04-25 01:48:46 UTC
After akonadi starts the system gets slow. LED for harddrive is alight constantly and computer takes minutes to react. Not even the mouse moves.

Reproducible: Always

Steps to Reproduce:
1. Start Kmail
2.
3.

Actual Results:  
Everything comes to a halt


The email is stored on a NAS not on the local computer. Indexing is disabled. Here is an example of the top command:
PR 20 |  VIRT 15206000  |  RES 1.280g  |  %CPU 0.993  |  %MEM 67.33       akonadi_notes_a
Each time I get similar values always over 50% of memory use. On an older computer with 2GB RAM and 2GB swap space this makes the computer unusable. 
I am no software developer so I cannot say more about the problem but was advised to file a bug report in the opensuse forum.
Comment 1 Denis Kurz 2017-06-23 19:56:16 UTC
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 2 Denis Kurz 2018-02-01 09:51:26 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.