#7976: Improve memory exhaustion process -----------------------------+---------------------------- Reporter: kallisti5 | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1/Development Resolution: | Keywords: Blocked By: | Blocking: Has a Patch: 0 | Platform: All -----------------------------+---------------------------- Comment (by axeld): If you ran out of memory, it's actually sane to not start new processes in favor of killing some random team. Besides yet, yes, we don't take such drastic measurements yet, and our low memory handling could surely be further improved. I'm not sure it's a good idea to randomly kill teams (or rather, I definitely know it's a bad idea, it's just the question of what alternatives you have). One way to deal with things like these is to notify the userland from the problem, and let it deal by taking down not so important services (and also notifying the user) -- unless you currently record something, this could be the media server, for example. Or player only apps like MediaPlayer or ShowImage. Once we have proper session management in place, a good alternative would be to just quit non-used applications that could be relaunched as they were when needed or possible. -- Ticket URL: <http://dev.haiku-os.org/ticket/7976#comment:2> Haiku <http://dev.haiku-os.org> Haiku - the operating system.