You are not logged in.
Hello,
Since recently (my system is up-to-date now), akonadi uses an enormous amount of memory on my system.
ps u -C mysqld
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
philipp 2058 1.2 57.2 3373980 2249272 ? Sl 19:22 0:01 /usr/bin/mysqld --defaults-file=/home/philipp/.local/share/akonadi/mysql.conf --datadir=/home/philipp/.local/share/akonadi/db_data/ --socket=/tmp/akonadi-philipp.qrGhWk/mysql.socket
With only 4GB installed, my system gets more or less unusable.
Stopping akonadi frees the memory, but on restart its memory usage gets as large as before.
Does anyone know what causes this problem/how to fix it?
Thanks in advance,
Philipp
Last edited by phi-mah (2016-11-07 20:43:11)
Offline
Ha, I'm not the only one; my mysqld eats 1,6 to 2 Gbyte Ram; I don't know, when it's happen exactly, because of 8 GByte Ram, I'm still able to work.
Unfortunately it does not happen with a new fresh user :-(
Wrong, it also happens for a fresh new user after start of akonadi; so it's not a configuration problem
I deleted:
~/.config/akonadi*
~/.config/baloo*
~/.config/kaddressbook*
~/.config/kmail*
~/.config/korganizer*
~/.local/share/akonadi*
~/.local/share/korganizer*
~/.local/share/kmail*
~/.local/share/baloo*
~/.local/share/local-mail
/tmp/akonadi*
then I rebooted -> did not help :-(
Any other ideas what could be culprit?
Last edited by midixinga (2016-11-07 19:09:49)
Offline
Same problæem here. I have 32 GB but my system from cold boot usually uses 1.2 GB now it uses 3.3 GB. According to top mysqld is eating that extra 2.1 GB.
Offline
it's jemalloc (what is jemalloc ???)
downgrade:
# pacman -U /var/cache/pacman/pkg/jemalloc-4.2.1-1-x86_64.pkg.tar.xz
solved my problem
Offline
it's jemalloc (what is jemalloc ???)
downgrade:
# pacman -U /var/cache/pacman/pkg/jemalloc-4.2.1-1-x86_64.pkg.tar.xz
solved my problem
Yeah, seems like a major regression was introduced in 4.3.0. 4.3.1 seems to be going out soon...
Offline
Yes, that did the trick. I will mark the problem as solved.
Many thanks,
Philipp
Offline
I opened a bug report for the issue
https://bugs.archlinux.org/task/51738
Offline
It seems that the issue got fixed upstream, jemalloc 4.3.1-1 is working again...
Last edited by phi-mah (2016-11-08 16:04:29)
Offline