42 ms·
The deeper concern here is this: > until the OS crashes How is it even possible that userspace crashes the OS due to memory exhaustion?
by zamalek 11y ago
The deeper concern here is this:
> until the OS crashes
How is it even possible that userspace crashes the OS due to memory exhaustion?
- viraptor 11y agoWhen you run out of memory something needs to be killed, or swapped. If you start swapping, you're not responsive anymore (you can generate data faster than writing it to disk). If you kill something, it may not be the application which needs to be killed. Usually systems don't come preconfigured with a hard per-app limit (which is a bad thing...), or oom score (systemd got this more popular though), so crashing the OS is still fairly easy.
- Piskvorrr 11y agoMaking the OS unresponsive, that happens, yes. But I have yet to see a modern OS crash - as in "OOM killed init or some other essential process".
- ekimekim 11y agoMy experience is that the OOM killer is generally pretty good at picking the right process to kill. At least on linux, it also considers whether the process has child processes, and kills them preferentially. These two aspect together mean that a linux system should consistently kill the tab loading the favicon and not, say, x11.
- Piskvorrr 11y agoWell, I did see an X11 server killed under unusual circumstances (not :0, but an Xvfb-for-Xpra; incidentally, this also killed its child, which was the offending process)
- deleted 11y ago[deleted]