How to stop entire VSCodium/VSCode window from being OOM killed in Fedora when it's better to kill the command in the integrated terminal that's the cause of high memory usage?
from dullbananas@lemmy.ca to linux@lemmy.ml on 23 Jun 23:46
https://lemmy.ca/post/46705599

It’s acting as if memory.oom.group is set to 1, even though it’s not:

dullbananas:~$ cat /sys/fs/cgroup/user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-codium-158608.scope/memory.oom.group 
0
dullbananas:~$ cat /sys/fs/cgroup/user.slice/user-1000.slice/user@1000.service/app.slice/memory.oom.group 
0
dullbananas:~$ cat /sys/fs/cgroup/user.slice/user-1000.slice/user@1000.service/memory.oom.group 
0
dullbananas:~$ cat /sys/fs/cgroup/user.slice/user-1000.slice/memory.oom.group 
0
dullbananas:~$ cat /sys/fs/cgroup/user.slice/memory.oom.group 
0
dullbananas:~$ cat /sys/fs/cgroup/memory.oom.group 
cat: /sys/fs/cgroup/memory.oom.group: No such file or directory

#linux

threaded - newest

[deleted] on 24 Jun 00:43 next collapse

.

catloaf@lemm.ee on 24 Jun 01:26 next collapse

How little ram and swap do you have that this is a problem?

You might just use ulimit: unix.stackexchange.com/a/746762/90708

I feel like there’s a better way to do this, unless you’re intentionally trying to run out of RAM.

pastermil@sh.itjust.works on 24 Jun 03:32 collapse

What commands are running in the integrated terminal? Wouldn’t it be better to run it on external ones?

enemenemu@lemm.ee on 24 Jun 12:28 collapse

Nice. This is such a stackoverflow answer. I love it

pastermil@sh.itjust.works on 24 Jun 13:50 next collapse

Lol, what make it so?

mactan@lemmy.ml on 24 Jun 18:19 collapse

looks like a question to me