You are not logged in.
I'm running KDE Plasma, and any time I open KSysGuard, there are a bunch of different processes running for Chrome. It happens with both the google-chrome AUR package and chromium from the official repositories. Rebooting frees up the memory, but it doesn't take long for it to get hogged again. Also, possibly related: occasionally when I start Chrome, it "takes a screenshot" and that becomes the window. I don't really know how else to phrase that. I can minimize the window and do other shit, but I have to restart chrome a couple of times to get it to work properly.
Any ideas?
Also, snapshot of what KSysGuard looked like this morning:
Offline
Expected behavior.
Offline
I use a bunch of switches in all my chromium .desktop files, these 2 may help you:
--purge-memory-button #turns on the ability to purge all the memory
--memory-model=low #select the model you want from low, medium or high depending on your resources, default is medium
as a last resort you can force chromium to run in 1 process with:
--single-process
bear in mind that when using these switches & you find a new install is mis behaving please remove the switches & run in a new fresh profile
Offline
--purge-memory-button #turns on the ability to purge all the memory
--memory-model=low #select the model you want from low, medium or high depending on your resources, default is medium
According to http://peter.sh/experiments/chromium-co … e-switches the 2nd switch has been deprecated.
Offline