[Bug 1966381] Re: systemd-oomd is counting cached as used and triggering more easily than it should

Fri Apr 8 11:42:37 UTC 2022

Was this released ? I've received an update of that package this
morning:

> $ dpkg --list systemd-oomd
> Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder
> | État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé/W=attend-traitement-déclenchements
> |/ Err?=(aucune)/besoin Réinstallation (État,Err: majuscule=mauvais)
> ||/ Nom            Version         Architecture Description
> +++-==============-===============-============-====================================
> ii  systemd-oomd   249.11-0ubuntu3 amd64        Userspace out-of-memory (OOM) killer

But even with that version which fixes the issue according to:

> systemd (249.11-0ubuntu3) jammy; urgency=medium
> 
>   * oomd: calculate 'used' memory with MemAvailable instead of MemFree (LP: #1966381)
>     File: debian/patches/lp1966381-oomd-calculate-used-memory-with-MemAvailable-instead-of-M.patch
>     https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=15fc4c53d726e1dcae7296a9306cfd453fd1a046
>   * hwdb: remove the tablet pad entry for the UC-Logic 1060N (LP: #1926860)
>     File: debian/patches/lp1926860-hwdb-remove-the-tablet-pad-entry-for-the-UC-Logic-1060N.patch
>     https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7bf31946a52e55f9f6ea4ecfa30e311685b20997
> 
>  -- Nick Rosbrook <nick.rosbrook at canonical.com>  Thu, 07 Apr 2022 15:28:15 -0400

I still hit the problem after a few minutes of building a debug firefox
on my laptop (ThinkPad P14s, 32GB RAM)

> -- Boot c45108609edc41368bc948d9ffda1f4d --
> avril 08 12:30:44 portable-alex systemd[1]: Starting Userspace Out-Of-Memory (OOM) Killer...
> avril 08 12:30:44 portable-alex systemd[1]: Started Userspace Out-Of-Memory (OOM) Killer.
> avril 08 12:42:07 portable-alex systemd-oomd[1168]: Killed /user.slice/user-1000.slice/user at 1000.service/app.slice/app-gnome-Alacritty-6631.scope due to memory used (26327048192) / total (29247873024) and swap used (1023406080) / total (1023406080) being more than 90.00%
> -- Boot 2d12cd6e16d4432b94f957fc1cd77124 --

This is what I can see in the logs ; as you can see it's killing my term
(alacritty).

FTR, all things being equal otherwise, I have been able to run for days
with systemd-oomd masked and disabled and the same usage.

-- 
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/1966381

Title:
  systemd-oomd is counting cached as used and triggering more easily
  than it should

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Jammy:
  Confirmed

Bug description:
  Just now I was watching some video in Firefox. I popped over to
  another virtual workspace for a few minutes, and when I popped back to
  Firefox it had gone. The same thing had been happening all week (I
  installed fresh Ubuntu-22.04 last week) with Chrome, Firefox and
  Thunderbird.

  This time instead of shrugging it off I looked in the logs, and found
  this

  Mar 25 19:45:40 ubuntu systemd-oomd[960]: Killed /user.slice/user-1001.slice/user at 1001.service/app.slice/app-gnome-firefox-6607.scope due to memory used (15940579328) / total (16153944064) and swap used (925564928) / total (1023406080) being more than 90.00%
  Mar 22 08:11:29 ubuntu systemd[5029]: app-gnome-google\x2dchrome-5412.scope: systemd-oomd killed 298 process(es) in this unit.
  Mar 23 11:09:28 ubuntu systemd-oomd[1055]: Killed /user.slice/user-1001.slice/user at 1001.service/app.slice/app-gnome-thunderbird-5418.scope due to memory used (15591993344) / total (16149745664) and swap used (927760384) / total (1023406080) being more than 90.00%
  Mar 23 11:09:28 ubuntu systemd[5029]: app-gnome-thunderbird-5418.scope: systemd-oomd killed 173 process(es) in this unit.

  I know it's saying those three entirely unrelated applications had
  suddenly decided to swallow all the RAM+swap on this laptop of mine -
  but the very same apps didn't act like that last week under
  Ubuntu-20.04, so I suspect something else is going on

  I can't say they hadn't swallowed all the RAM, but there is ZERO sign
  of a system on the verge of collapsing - everything has been screaming
  along just nicely - no sign of the "staggering" you normally get when
  the OS is heavily into swap.

  However, now that I look I see my 16G laptop only has 1G swap??? I
  just let the Ubuntu installer do it's defaults - but it used to auto-
  choose 1xRAM or 2xRAM - what's with this 1G swap? Could that be
  related?

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: systemd-oomd 249.11-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 25 19:47:44 2022
  InstallationDate: Installed on 2022-03-13 (11 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

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