Accidentally wrote a dead loop that hogged both CPU time and RAM. Waited for kernel to kill it, but 5 min after nothing happened, so I restarted the computer. In theory Linux Kernel should start killing processes once RAM is drained, so what's going on here? #askfedi

@Hanuwu My understanding is that if you use swap on a fast-enough disk, there can be enough activity for the kernel to not trigger OOM.

On my machines I usually use either earlyoom or thrash-protect to prevent this.

Further reading, if you're interested:

- news.ycombinator.com/item?id=2

@casualwp Hmm, so if I disable swap this could trigger OOM? I do have swap set up on HDD.

Follow

@Hanuwu Likely yes. Indeed, I've seen people who disable swap explicitly because they want OOM to kick in as soon as possible.

Sign in to participate in the conversation
CleverLibre Social

CleverLibre Social is an inclusive social instance for open discussion, learning, and community.
All cultures welcome.
Hate speech and harassment strictly forbidden.