[Akonadi] [Bug 390260] akonadi-ews-resource segfault

[Kai Krakow]

https://bugs.kde.org/show_bug.cgi?id=390260

--- Comment #3 from Kai Krakow <kai at kaishome.de> ---
I removed Akonadi completely because it started to accumulate gigabytes of RAM
over time since one of the last updates (the processes growing to 9 GB of RAM
usage). And there's even not a sane mail client to actually use Akonadi's
potential. KMail is still very unstable, slow, and buggy. So I moved away and I
am currently using Mailspring instead. I may try the KDE PIM suite some day in
the future again because I'm missing the calendar feature.

The next thing to go away is probably baloo because it got slow. Its processes
tend to grow to 3-4 GB of RAM usage and eat a lot of IO performance during that
process, the system feels very laggy until I kill the processes. Also, it
started to re-index all my files on every reboot.

In both cases I tried recreating the databases (Akonadi and Baloo) from scratch
but it didn't solve the problem.

I'm feeling a bit sad about this because usually I enjoyed the good integration
of the KDE components into the complete desktop. But if it makes a quite potent
system to vastly slow down for extended periods of time, I have no other
choice. I needed to remove all PIM components completely to get back a snappy
and stable KDE desktop. :-(

I wonder why this hit me lately: I've run with both Baloo and Akonadi for years
and never experienced the problems one could read about in hundreds of forums,
namely that those services slow done people's systems. Now it happened to me,
too, and the impact is really very big.

Baloo and Akonadi really need some love, and I wish I could be part of this by
contributing help with identifying and fixing bugs. But the negative impacts it
had on my productivity were just too big. I'm sorry.

-- 
You are receiving this mail because:
You are the assignee for the bug.