Other than the huge leak on initial indexing, akonadi baloo feeder creates *massive* IO output - it makes both PIM, and the computer unusable =( Maybe it depends on DB size... Reproducible: Always Steps to Reproduce: Install baloo/akonadi/kdepim master or 4.13 branch/beta Actual Results: See enormous amount of IO created Expected Results: =) let me know how i can help debugging. so far i've wiped the DB twice, didn't helped.
adding Dan to CC, i know he said on IRC he has the same effect...
I can confirm that (openSUSE 13.1, KDE 4.13.0). Isn't it related to https://bugs.kde.org/show_bug.cgi?id=333655 ?
(In reply to comment #2) > I can confirm that (openSUSE 13.1, KDE 4.13.0). Isn't it related to > https://bugs.kde.org/show_bug.cgi?id=333655 ? could be related, though likely different causes. i've got situation more-less under control by wiping 2/3 of my mails, and ommiting one collection with fair share of attachments from indexing
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present? If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
After some time of peace, I do hit it again in baloo 5.26.0 (openSUSE TW, Plasma 5.8.2)...
(In reply to Vojtěch Zeisek from comment #5) > After some time of peace, I do hit it again in baloo 5.26.0 (openSUSE TW, > Plasma 5.8.2)... Recent kdepim version don't use baloo. That's probably unrelated.
OK, so this is another problem and this bug can be closed.