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

[John S]

For me I have 32GB of ram and it was killing my entire user session and
dropping me back to the GDM. (It took me over a week to realise this was
happening and I was kicked back to login losing all work at least 15
times, having to log back in produced a lot of log spam that hid the OOM
message, I was close to having to reinstall or switch distro to fix it)
I was using i3 but this was totally unusable for me and I had to remove
the service. Does it just not play nice with applications that grab as
much RAM as possible and free it when the system is under pressure?

Personally if this isn't fixed and OOM gets turned back on at some point
it would be severe enough for me to switch distro.

-- 
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:
  Incomplete

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