Bug 356903 - akonadi notes agent use 800Mb of RAM all the time
Summary: akonadi notes agent use 800Mb of RAM all the time
Status: REPORTED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 4.13
Platform: Fedora RPMs Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-19 11:40 UTC by Mark Stanton
Modified: 2021-03-09 05:46 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Stanton 2015-12-19 11:40:58 UTC
I use Kontact (4.14.10 under Plasma5, Fedora22), and the akonadi_notes_agent always occupies around about this much memory.

I have very few notes, but it seems ALL my email is also listed in a notebook. I don't want this, I'm not aware of having set it up like this, I don't seem to be able to stop it.
If I select "Notes" in Kontact then its RAM usage goes up around 1.25Gb and 50% cpu usage.
I haven't been able to find a solution either from the help or the IRC channel(s).

Reproducible: Always

Steps to Reproduce:
1. Turn on computer
2.
3.
Comment 1 Sunito 2016-01-10 17:16:21 UTC
I use KMail 4.14.2 and also observe a very high memory consumption (6 to 7 GB) of akonadi_notes_agent.
I don't think that I've ever used any notes in KMail.
Comment 2 Sunito 2016-01-10 21:59:34 UTC
I have now solved this for me by deleting the notes agent as suggested here:
https://www.kubuntuforums.net/showthread.php?65497-Akonadi-Notes-Agent-hogs-memory

Actually, in my case, deleting the Notes agent in the kcm_akonadi GUI was not enough.
Only after I have manually deleted all lines containing "notes" or "akonotes" in .config/akonadi/agentsrc
and then deleting the notes agent via kcm_akonadi again,
the akonadi_notes_agent is gone (for good, I hope).
Comment 3 Justin Zobel 2021-03-09 05:46:46 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.