The memory required by KDE is abnormally high


#1

Hi,
Since some weeks (aprox. update from Jan. 2019) the memory consumption of my system seems too high. A plain start of KDE without any running programme needs up to 1 GB RAM!

The picture shows the output of htop.

I know that baloo / akonadi needs some system resources.
I’m wondering why /bin/baloo_file runs twice and /bin/plasmashell runs several times.
Is this normal behavior?

In December my system still had a memory load of about 600 MB after a reboot.

How con I clean up my system?

Thanks in davance
mepi0011


#2

Can’t confirm this as on boot mine takes around 620MiB > 3 Activities, Latte-Dock with different layouts on a dual display setup.
Try a TEST user and see if the memory is still high in that session. If not, then you have to take a closer look at your user configs.


#3

Do you also have Akonadi suit installed? In my experience whenever I was using Kmail/Kontact RAM was going up to something around 900MB+1GB (I also had Dropbox).

To @mepi0011, you may also check with ps_mem. As far as I know, baloo is for file indexing, so maybe you have some new big directory added and it does indexing? Also there are threads in the web/forum about how resetting/optimizing baloo. Worth to look into.


#4

Nope, nor clients fo cloud or chat …


#5

There is a QT memory leak bug affecting some.


#6

Forum search first is best, there are a few threads on this already.

There is a current issue with Qt 5.12.1 and use of the Oxygen theme causing abnormal plasmashell memory usage, and other issues like not being able to launch apps from menus.

Best course of action currently is to change to another theme, like Breeze, until upstream patches arrive.


#7

On my laptop I see 850MB at start, that’s with a small Conky and a weather widget. It has been much less, around 500 or so.


#8

Used to have a lot of things running at startup, and a very convoluted setup for Activities/Virtual Desktops/Widgets/Latte-Dock … I reduced all that to the point that all looks almost boring, but has the same efficiency for my workflow, but uses less than half memory of what it used too. On another system it uses only 430MiB.