3 ms·
Does it has to be inexplicably? Is there any reason the OOM Daemon can't nicely prompt you about what process they just killed? Or even ask you if you want to k
by omeid2 3y ago
Does it has to be inexplicably? Is there any reason the OOM Daemon can't nicely prompt you about what process they just killed? Or even ask you if you want to kill, similar to how Firefox will ask you if you want to kill a misbehaving tab?
- guappa 3y agoIt just picks a big one at random. Like the shell in which you're running make, and then you have a mess. Even worse when it kills containers.
- Santosh83 3y agoI guess they could attempt to do so, but under extremely severe low memory conditions, the prompt (especially if its graphical) has a good chance of not reaching the user's screen in any reasonable time. That's why it has to decide without external I/O.
- omeid2 3y agoYou can suspend a process, drop some caches, and even swap them to disk, if the memory approaches critical levels, or better yet, you can set a watermark that suspend the process and prompts you before it gets to that.