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
  • wakko@lemmy.world
    11·
    19 days ago

    How do you control the oomkiller? Short answer - You don’t. That’s by design. You can google for the lkml discussions about it.

    What you can do is set cgroups around vsc to limit its resource consumption to improve your odds of avoiding the oomkiller’s attention entirely. Google up the cgroups docs for details.