Re: akonadiserver and kmail are leaking memory

In data domenica 31 marzo 2019 18:05:32 CEST, Hans-Peter Jansen ha scritto:
> Hi,
> 
> after finally moving to Tumbleweed from some KDE 4 based akonadiserver and
> kmail setup, I noticed them to exhaust my systems 32G memory:
> 
> hp       14482  5.6 83.7 41289736 27545972 ?   Sl   13:03  15:34 /usr/bin/
> akonadiserver
> hp       14912  0.1  2.2 6302588 743184 ?      Sl   13:04   0:28 /usr/bin/
> kmail -qwindowtitle KMail
> 
> Yes, that reads 41G VSZ and 27G RSS for akondiserver, only in about 5 hours
> wall clock run time.
> 
> The KDE 4 versions where almost stable for the same setup, that consists
> from some huge IMAP mailboxes, indeed.
> 
> Does somebody know, if the upcoming kdepim versions behave better in this
> respect? In other words, is it advisable to try?
> 
> Thanks,
> Pete

Leap 15.0
Bug 1100080
Try to uninstall baloo indexer. When it crashes then kmail leaks huge amount 
of memory up to shutdown or unresponsiveness. 
The bug is known to kde and it is linked to lmdb.
While to TW it was cherrypicked and backported (there is a fix) the Leap 15 
version did not receive this blessing up to now. 
with mysql, the system does not complain always, only sometimes rarely konqi 
pops up after baloo crashed. 
If you use postgres you will instead receive an instant konqi list of the 
crash. You can compare the backtrace in the bug. Don't know why. 
The number of the kde original bug with indications about the fix you find it 
in the title.

If it is you will see in ksysgard:
a kontact session that stays open even if you shut it down from "exit the 
program" (zombi), a korgac instance, akonadi with huge memory consumption, and 
a huge number of http.so instances that will go away only after doing the 
following:
kill the processes of kontact, korgac
then in the terminal: akonadictl stop
wait for the akonadi and  http.so are gone, you will see the memory normalize. 
Kill then baloo indexer if he still lingers around and kill all other baloo 
instances if open.

simply restart kontact and you system will run for weeks as long as:
you do not suspend to disc or to ram. Than the whole thing may start over (or 
you wlan disappears, or you do not have access to the wallet etc. All little 
bugs that will be fixed one day). 
But if you running a system for long time without suspending it, (days, weeks) 
then this method works. 
Always said you are not running into some other kmail/kontact/akonadi bug. 
Good luck.




_________________________________________________________________
________________________________________________________
Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de


-- 
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]