Overview
Request History
embar- created request
- include Falkon browser and mpv media player among
the list of programs to terminate preferably
factory-auto added opensuse-review-team as a reviewer
Please review sources
factory-auto accepted review
Check script succeeded
licensedigger accepted review
ok
staging-bot added openSUSE:Factory:Staging:adi:4 as a reviewer
Being evaluated by staging project "openSUSE:Factory:Staging:adi:4"
staging-bot accepted review
Picked "openSUSE:Factory:Staging:adi:4"
dimstar_suse added factory-staging as a reviewer
Being evaluated by group "factory-staging"
dimstar_suse accepted review
Unstaged from project "openSUSE:Factory:Staging:adi:4"
dimstar accepted review
dimstar_suse added openSUSE:Factory:Staging:adi:22 as a reviewer
Being evaluated by staging project "openSUSE:Factory:Staging:adi:22"
dimstar_suse accepted review
Picked "openSUSE:Factory:Staging:adi:22"
dimstar_suse accepted review
Staging Project openSUSE:Factory:Staging:adi:22 got accepted.
dimstar_suse approved review
Staging Project openSUSE:Factory:Staging:adi:22 got accepted.
dimstar_suse accepted request
Staging Project openSUSE:Factory:Staging:adi:22 got accepted.
Earlyoom always kills firefox completely. But if I execute "killall Web\ Content" from the console, I get a lot of memory freed up, while firefox itself remains working. Maybe all the same it makes sense to specify "Web\ Content" before "firefox", so that earlyoom, if possible, would kill only the problematic tab? I don't know exactly how earlyoom works. Does Earlyoom track the process name or just the name of the executable?