[Bug 1972159] Re: systemd-oomd frequently kills firefox and visual studio code

[Nick Rosbrook]

> $ cat /etc/systemd/system/-.slice.d/10-oomd-root-slice-defaults.conf
> [Slice]
> ManagedOOMSwap=auto

I have been running with this configuration this week, and have been
running a script to log occurrences of my memory and swap usage each
exceeding 90%. I have had several such occurrences, but have yet to
experience any noticeable performance issues. For example, this morning
`oomctl` reported the following usage, but I was able to continue using
my system without any noticeable difference:

$ oomctl 
Dry Run: no
Swap Used Limit: 90.00%
Default Memory Pressure Limit: 60.00%
Default Memory Pressure Duration: 20s
System Context:
        Memory: Used: 14.3G Total: 15.5G
        Swap: Used: 979.9M Total: 979.9M
Swap Monitored CGroups:
Memory Pressure Monitored CGroups:
        Path: /user.slice/user-1000.slice/user at 1000.service
                Memory Pressure Limit: 50.00%
                Pressure: Avg10: 0.00 Avg60: 0.00 Avg300: 0.00 Total: 6s
                Current Memory Usage: 13.5G
                Memory Min: 0B
                Memory Low: 0B
                Pgscan: 13490147
                Last Pgscan: 13490147

This is just one data point of course, but it puts me in favor of
disabling swap kill for Jammy.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1972159

Title:
  systemd-oomd frequently kills firefox and visual studio code

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Kinetic:
  Confirmed
Status in systemd package in Fedora:
  Unknown

Bug description:
  Since I installed Ubuntu 22.04, firefox and visual studio code are
  frequently killed by systemd-oomd (every 2hours).

  I have 8 GB memory and never experienced this before the upgrade to
  Ubuntu 22.04. I thus assume that the claim that there is not enough
  memory is abusive. Did 64GB of memory become the minimum requirement
  to run Ubuntu ?

  The second problem is that it gives a very bad user experience which
  is critical for new Ubuntu users.

  There should be a warning prior killing apps to give the opportunity
  to save the app data. There should at least be an apologize and an
  explanation after killing the app.

  The current behavior gives the impression that Ubuntu 22.04 is
  unreliable and unsafe to use which is a problem for an LTS release
  that many people might want to use for critical production context.

  There might be a configuration problem with systemd-oomd or simply a
  bogus behavior. I would recommend to disable it or remove it
  completely until this problem is resolved. This is what I will do for
  myself because I have work to do.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1972159/+subscriptions