Comment 57 for bug 1972159

I agree.

I might add though (and this is my first time on linux forums, so I'm not sure how this is generally addressed) that this problem can easily affect non-technical end users as well, which would likely not be comfortable with shell commands such as top or systemd-cgtop. In case it is helpful, I'll attach a screenshot of how macOS solves this problem through a GUI interface for force-quitting that includes current memory usage for each application. I think this is a nice way of empowering the user to make the decision. However, I could not find an existing linux/GNOME GUI that does something similar.

In the meantime, perhaps improving the heuristics of the resource manager so core services like GNOME Shell are not killed would be helpful. And I think that so long as auto-killing is the active solution, it would be nice for any apps that are killed due to memory constraints for there to be a system alert informing the user as to this decision, since the event otherwise seems quite anomalous.