systemd-oomd issues on desktop
Julian Andres Klode
julian.klode at canonical.com
Fri Jun 10 09:40:52 UTC 2022
On Thu, Jun 09, 2022 at 03:19:36PM -0400, Dan Streetman wrote:
> > I think that either option (1) or (3) would be the most reasonable --
> > maybe trying (1) first and falling back to (3) if necessary. If anyone
> > has an opinion on this, or can think of other options, I would
> > appreciate the input.
> Was systemd-oomd enabled by default for a specific reason? The kernel
> is quite able to handle oom situations itself, and has been for years,
> so while I'm not trying to suggest systemd-oomd is without any use
> case, I'm skeptical that systemd-oomd should be enabled *by default*.
> I think it's more likely to behave better when enabled to address a
> specific system use case, and leave the default behavior of handling
> oom to the kernel.
No what the kernel does is it starts stuttering, the system becomes
unresponsive and eventually needs a hard reset maybe.
The bug reports we see show that systemd-oomd is working correctly:
The browser gets killed, the system remains responsive without having
become unresponsive as would be the usual case.
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer i speak de, en
More information about the ubuntu-devel