Public
Federated
Thread

[[email protected] ~]$ :idle:
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 - https://uwu.social/tags/askfedi

uwu.social
A public Mastodon instance since May 2018.
Everyone is welcome... as long as you like to uwu.

Cordelia Green
replyReply to @[email protected]
Hanuwu - https://uwu.social/@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: https://news.ycombinator.com/item?id=26450960 - https://news.ycombinator.com/item?id=26450960

[[email protected] ~]$ :idle: (@[email protected])
1.56K Posts, 62 Following, 78 Followers · 24 yo KDE contributor based in China (PRC)
member of uninterested party
male
MischievousTomato
replyReply to @[email protected]
@casualwp@qoto.org @Hanuwu@uwu.social Since I have a 5400rpm disk, I use zram. So much better

Reptiltejosh63
replyReply to @[email protected]
@MischievousTomato@poa.st @Houkago_Jimtime@poa.st @Hanuwu@uwu.social @casualwp@qoto.org That explains my asshole.

Lars Sadbro
replyReply to @[email protected]
@MischievousTomato@poa.st @Houkago_Jimtime@poa.st @Hanuwu@uwu.social @casualwp@qoto.org well that makes sense because i misread your first post as "5400rpm dick"