Ubuntu
systemd package

  1. Bug #1966381
  2. Comment #14

Comment 14 for bug 1966381

Revision history for this message
Pirouette Cacahuète (lissyx) wrote :

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 <email address hidden> 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@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.