On 03.01.2020 20:18, Ben Cotton wrote: > Workstation working group has discussed "better interactivity in > low-memory situations" for some months. In certain use cases, > typically compiling, if all RAM and swap are completely consumed, > system responsiveness becomes so abysmal that a reasonable user can > consider the system "lost", and resorts to forcing a power off. This > is objective a very bad UX. I'm strongly against adding of any user-space OOM killers to Fedora default images. Users should explicitly enable them only when needed. 1. Such applications run with super-user privileges and has full access to all private memory of all processes and sensitive user data. This is a huge security breach. 2. It can easily kill KDE/Gnome shell or VM hypervisor, which can cause data loss. 3. Some implementations are killing all processes with the same name[1] and their developers think that this is a feature. 4. Super-user daemons should not touch userspace at all. A real user-space OOM should run with privileges of the same user using system-user units. [1]: https://gitlab.freedesktop.org/hadess/low-memory-monitor/issues/8 -- Sincerely, Vitaly Zaitsev (vitaly@xxxxxxxxxxxxxx) _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx