2 May
2016
2 May
'16
22:22
Hi,
On Mittwoch, 27. April 2016 17:24:04 CEST Luca Beltrame wrote:
It's likely unrelated then. Installing debug symbols and providing a backtrace to the 100% CPU process would be helpful in finding the issue.
I finally managed to get the bad guys. Attached are the tracebacks of the two akonadiserver processes using about 1 CPU each
But before that, does this also occur on a network loss?
No. However it seems that: after a reboot everything works fine for some suspend-resume cycle. Then something happens and akonadi begins miss-behaving after at every resume. Let me know if you need more info and/or if I should file a bug at kde Ciao, Francesco