[Bug 2075104] Re: user session is randomly terminated by systemd-oom when the system is left alone for a while

[Jurgen Schellaert]

systemd-analyze cat-config systemd/oomd.conf:

# /etc/systemd/oomd.conf
#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it under the
#  terms of the GNU Lesser General Public License as published by the Free
#  Software Foundation; either version 2.1 of the License, or (at your option)
#  any later version.
#
# Entries in this file show the compile time defaults. Local configuration
# should be created by either modifying this file (or a copy of it placed in
# /etc/ if the original file is shipped in /usr/), or by creating "drop-ins" in
# the /etc/systemd/oomd.conf.d/ directory. The latter is generally recommended.
# Defaults can be restored by simply deleting the main configuration file and
# all drop-ins located in /etc/.
#
# Use 'systemd-analyze cat-config systemd/oomd.conf' to display the full config.
#
# See oomd.conf(5) for details

[OOM]
#SwapUsedLimit=90%
#DefaultMemoryPressureLimit=60%
#DefaultMemoryPressureDurationSec=30s

# /usr/lib/systemd/oomd.conf.d/10-oomd-defaults.conf
[OOM]
DefaultMemoryPressureDurationSec=20s

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

Title:
  user session is randomly terminated by systemd-oom when the system is
  left alone for a while

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I was surprised last week to find that my computer had logged me out
  when I had left it alone for some 15 minutes.  I did not bother to
  research at the time and did not see any reason as the problem did not
  manifest again .

  Then today, it happens again. The circumstances are similar: I leave
  the system long enough for the screen to power off and come back to
  find myself kicked out of my session. Yes, kicked out, not simply
  locked out. I need  to log in again and find that all running apps and
  open files have all been  closed.

  My journal would appear to show that gnome-shell got stopped as a
  consequence of systemd-oomd killing several applications (see the
  included journalctl snippet - mind that the output is in reverse order
  (journalctl -r)).

  Should not  oomd terminate single applications instead of complete
  user sessions?

  And I do have some doubts about the statistics listed in the journal.
  One of the killed  apps is reported as consuming over 22GB or RAM (out
  of 32). I have been using that app for many years and cannot remember
  having see it use more than a few GB.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: systemd-oomd 255.4-1ubuntu8.2
  ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8
  Uname: Linux 6.8.0-39-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 30 04:00:27 2024
  InstallationDate: Installed on 2022-03-27 (855 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  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/2075104/+subscriptions