It would be good to submit logs at Latte docks bug tracker to help @psifidotos fix those 
Removing might be a quick fix in your case but it doesnt help the application improve - to me its one of best things happening to KDE desktop wise 
7 Likes
When I saw that Latte-Dock consumes 30 GB of RAM, I immediately deleted it. I do not use it, I like the standard lower panel KDE. After installing the system, I simply hid it, but it remained in the background and ate 1/4 of my RAM))). And this is precisely a memory leak, he first consumed 200 ~ 300 MB of memory, and a few days already 30 GB. And because of the Latte-Dock, I also lagged KDE. After deletion, all problems disappeared. Unfortunately I have no logs.
1 Like
If that were true, you wouldn’t be the only one in the world who would have noticed that.
For me, the biggest RAM “consumer” is the Internet browser. KDE, Kate, Telegram, FireDragon = < 7GiB
4 Likes
It was more than a month ago. During that time, the developer could well fix it. My computer works 24/7. And this problem I had 5 days after switching on. The usual user who often reboots the PC, and would not notice this. But the strangest thing is that in addition to the leakage of memory, I was very much lagged KDE. There were friezes for a few seconds. However, I do not quite ordinary computer. But because of this, the memory leakage definitely could not happen.
Sometimes it is not (or not only) a problem of latte (or KDE) memory usage, but the used applets. E.g. at a quick search I found this:
https://bugs.kde.org/show_bug.cgi?id=435579
2 Likes
I call bullshit. If there’s no journal log it didn’t happen.
3 Likes
I will sometimes experience lags after a large update, until I perform a btrfs balance and then a reboot. While a reboot is unnecessary on Linux most times it will often cure strange quirks. A btrfs balance and reboot often cures a lag or micro freeze/stutter type situation.
5 Likes
I have a hardware RAID at read / write speed ~ 1.5 GB / s. This is definitely not a problem. After each update, I always make a balance and defragmentation. Even when I did not do this, the speed of the file system did not fall below 1 GB / s. I have old servers on SCSI drives, on them without a balance everything becomes quite bad.
PS: I installed Latte-Dock and left it in the background. Let's see what happens to him in a few days.
1 Like
hum... maybe the user was looking at the "Virt" memory tab ?
That has some crazy stuff... like baloo using 256G or element/riot using 56G...
although everything works in my low RAM computer ( I only have 16G ) ( because of course it does, virt means nothing ).
Also... one thing I noticed when I was testing garuda in a VM yesterday -> kde blur settings are set to MAX.... this makes blur very intensive. Making blur half or just a little lower makes it much speedier.
Also taking into account that garuda enables psd by default .. in slow discs it can make things lag while synking ( i think )
PSD syncs browser profiles at the user level. It consumes only a hundred or so MBs of RAM. It never slowed anything down on my old 5400 rpm spinner.
1 Like
It consumes only a hundred or so MBs of RAM.
let me introduce you to my firefox profile:
du -sch @firefox
2,4G @firefox
2,4G total
Anyway, i wasnt discouraging using psd or that it was FOR SURE a problem. ( really depends on what it has to sync )
I use it myself also, and also anywhere-sync to sync .cache.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.