On 13/01/2020 09:33, Carlos E. R. wrote:
But who is the culprit of the OOM, the last process that requests memory and fails? Maybe there is a much earlier process that is leaking memory and ate most of it, so that the last process is just the last drop in the vase.
A very good point! As I said, BAD DOCCO. So long as you can keep coming up with justifications like that, you are pointing out the inherit design flaws that the designers never considered. Good for you, bad for them. The problem with reporting that as a bug is that they are likely to simply dismiss it. Personally, I think that is a VERY realistic scenario!
It can happen that one is running a long calculation that takes a lot of memory; maybe I would prefer something else killed rather than this one, so that the big one finishes.
Agreed. Indumitedly!
Maybe instead of killing a big process, it could be sent to sleep and swapped to emergency file, to be recovered and restarted later. The admin is sent an email so that he takes action (like creating more swap temporarily, or killing something else: he decides).
Maybe instead of killing, the system can create temporary swap file and mail the admin.
maybe a lot of things. maybe a lot of code. maybe a case for UI design. "Who are you going to kill today, Mr Admin" oh, look, all those background processes started by systemd that are questionable value in this context, like the print system, but if I kill them off using your "chose one of the above" UI systemd just starts them again ... It does strike me as a lot of code to go into the kernel and the gurus thereof will, I suspect, argue that this is such an exceptional case that it doesn't warrant that much effort. Heck, I've encountered that even with applications. Oftentimes the design is architecture so as to make fixing such problems difficult. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org