It's 2026 and I still can't configure the OOM killer to kill firefox before anything else.

bellowsgulch 5 hours ago | parent | next [-]

I looked into this, and actually, it seems like maybe you can? https://man7.org/linux/man-pages/man5/proc_pid_oom_score_adj...

So, in actuality, I think your assertion just taught us all something, because despite knowing that the OOM killer and that the Magic SysRq key[1] exists, I didn't know you could configure this as an input!

[1]: https://en.wikipedia.org/wiki/Magic_SysRq_key

▲

rwmj 5 hours ago | parent [-]

I'm aware of it, but it's awkward to use in practice. You have to track down all the FF processes, each time you run it, and adjust all their scores.

	▲	nick__m 38 minutes ago \| parent \| next [-]
		You could launch it as a systemd user target with OOMScoreAdjust=500 in the service section; weird and unconventional but wrapped in .desktop file it doesn't appear to be unwieldy.
	▲	bellowsgulch 26 minutes ago \| parent \| prev \| next [-]
		Ah. Yes, that is awkward. Well, nonetheless, you taught me a new feature. Thanks!
	▲	jitl 29 minutes ago \| parent \| prev \| next [-]
		sounds like a job for a program
	▲	loeg 4 hours ago \| parent \| prev [-]
		Maybe firefox could self-adjust, as a policy?

▲

SoftTalker 5 hours ago | parent | prev | next [-]

I always wanted it to target java processes, as they were always the culprit. These days it's python, VSCode, and antigravity.

▲

dvh 6 hours ago | parent | prev | next [-]

This. It's always browser running amok. I configured win+k shortcut key to: killall -9 chrome

▲

yjftsjthsd-h 4 hours ago | parent | prev | next [-]

Maybe not in kernel, but running the earlyoom daemon will let you do exactly that in userspace.

▲

IsTom 5 hours ago | parent | prev | next [-]

It's not a panacea, but in my case setting browser.tabs.unloadOnLowMemory in about:config helped a bunch.

▲

5 hours ago | parent | prev [-]

[deleted]