Summary: | akonadi_davgroupware_resoure takes a lot of cpu and memory | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | Johann-Nikolaus Andreae <johann-nikolaus> |
Component: | DAV Resource | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | major | CC: | auxsvr, bugs.kde.org, greg, kdebugs |
Priority: | NOR | Keywords: | investigated, triaged |
Version: | 4.9 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Johann-Nikolaus Andreae
2012-11-27 05:37:15 UTC
Do you have an idea of the total number of items you have in your calendars and addressbooks? I have 92 contact entrys, about 50 task and one events in the cloud. Another detail i found in 4.9.97: The resource make a lot (current 38GB) of output to the .xsession-errors. Always the same line: akonadi_davgroupware_resource_0(2644)/akonadiserializer (addressee) Akonadi::SerializerPluginAddressee::deserialize: Empty addressee object! I just had it nearly kill my system using all memory + swap after it thought it encountered invalid cert on davical server. (In reply to tony den haan from comment #4) > I just had it nearly kill my system using all memory + swap after it thought > it encountered invalid cert on davical server. I can confirm this for 4.12.5. I encountered the same type of behavior: after a problem verifying the server certificate (dav part of akonadi seems to be unable to properly deal with being offline while starting up) the process took all resources of one of my two CPU cores and started eating up GB of RAM (killed it before it took down my system). I've encountered problems with certificates and the davgroupware resource, but in my case the culprit was kded, as it was not responding. After restarting it, the davgroupware resource resumed proper operation. I had a certificate expired yesterday, and the resource behaved fine. No high CPU or RAM usage. I'm using 4.14.1, can anyone test on this version? Cheers, Grégory This bug has had its resolution changed, but accidentally has been left in NEEDSINFO status. I am thus closing this bug and setting the status as RESOLVED to reflect the resolution change. |