News for hackers. Stuff that matters.
Re:I've now disabled systemd-oomd on my Fedora desktops by eadmund on Thursday December 08, 2022 @01:18PM (#33911163)
That depends on what you mean by ‘crashing,’ doesn’t it?

One could at least fail gracefully: at start-up, request enough memory for a buffer reading ‘request to allocate memory failed; exiting’ and then print it to standard output, then exit.

One might initiate a garbage collection cycle.

One might even allocate enough buffers at start-up to cleanly process outstanding work, write results and then terminate.

It requires a little thought and engineering, but there are approaches which don’t just dump core.

Re:I've now disabled systemd-oomd on my Fedora desktops by tinus_hn on Friday December 09, 2022 @07:30AM (#33920518)
For very large values of ‘a little’. Just like that other poster with the ‘easy’ solutions, I challenge you to actually implement a demonstration of those easy ideas.

You can actually take some ideas from the Linux kernel if you like because it has what you propose, a way to allocate memory that never fails and never blocks. And there you can tell how easy that is.