On Monday 01 November 2010 09:17:04 Mike Barnard wrote: > Hi, > > On Mon, Oct 25, 2010 at 2:05 PM, Mike Barnard <mike.barna...@gmail.com>wrote: > > as mentioned above, I think my PIM not working well is due to akonadi > > crashing... I'll pay more attention to it next time it acts up and check > > what is not running and what has dumped core. > > OK.. I had some time to take a look at this and try and figure out what was > going on. > > Akonadi consumes almost all my 2GB of memory and eating about 36% of CPU > when things get slowed down, Xorg is spiraling out of control, eating about > 60% of CPU and some 1GB of memory.
I only use KMail (without Kontact) and I've never seen akonadi use so much resources. It does look like akonadi is misbehaving, perhaps upstream can help with that. > If I kill kontact, the 2GB memory is released and Xorg drops to about 16% > of CPU, but still eats up about 1GB of memory. > > I updated my ports collection and updated all out-of-date ports and still > the same behaviour. I notice that there have been a few patches, I am > updating my ports collection again this morning and will get any ports out > of date back up-to-date and check again. Recompiling everything may fix it. It is possible some dependency is not ABI forward compatible. > PS: Akonadi is not crashing this time round, it just consumes lots of > resources. Any one with ideas on what to check for, I'll get on it. You can also try cleaning out akonadi resources, such as: # rm -rf ~/.local/share/akonadi # rm -rf ~/.config/akonadi (make sure you back up, may eat your data)
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information