Comment 56 for bug 1972159

>Mar 25 19:00:46 fedora systemd-oomd[1612]: Killed /user.slice/user-1000.slice/user@<email address hidden> due to memory used (16360116224) / total (16541884416) and swap used (7752622080) / total (8589930496) being more than 90.00%

That something is being killed off at 90% swap usage makes sense, but not GNOME Shell. That's exchanging one big problem for another big problem, I'm not sure we can ever consider killing the desktop itself as a solution to the swap perf problem. And it makes me wonder if the only thing we can do is ensure resource control limits everything well enough that the user has the ability to choose what program needs to get killed off rather than doing it for them? As in, I'm wondering if oomd really should only be killing the most obvious candidates, and actually permit the less obvious candidates while still constraining the resources they can use to like 90% or whatever allows the shell+terminal to remain responsive enough (i.e. not perfect) such that the user doesn't reach for the power button. But instead reaches for top or systemd-cgtop to find out what's hogging resources, and decides whether to clobber it or not?