[Bug 1985887] Re: systemd kills gnome-shell or gnome-terminal if gnome-terminal uses much memory (50% over 20s)

[Daniel Johnson]

I've had two more instances, one on the 18th and one (multiple,
actually) today.  Both were triggered by copying a file as I'd described
(from CLI, "ionice -c3 nice cp -a SRC DST").  Today's OOM events also
killed a Firefox window for some reason.  I captured an sosreport on
both days, but last week's event showed I'd neglected to activate
sysstat/sar.  I am only uploading today's sosreport, but if the older
one may be useful I can add it as well.

All of the recent OOMs had this reason, with a varying initial percentage:
"due to memory pressure for /user.slice/user-1000.slice/user at 1000.service being 99.00% > 50.00% for > 20s with reclaim activity"


** Attachment added: "SOS report and systemd-oomd status"
   https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1985887/+attachment/5619231/+files/sosreport_20220926.tar

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

Title:
  systemd kills gnome-shell or gnome-terminal if gnome-terminal uses
  much memory (50% over 20s)

Status in OEM Priority Project:
  Invalid
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  [Steps to reproduce]
  0. Install Jammy image
  1. open gnome terminal
  2. issue stress_ng or Canonical certification tool checkbox as
  "checkbox-cli run com.canonical.certification::memory/memory_stress_ng"
  or
  "stress-ng --stack 0 --timeout 300"
  3. Terminal or Gnome-shell will be killed by systemd-oomd

  It's because all stressors are under same cgroup belongs to terminal.

  Both Wayland and Xorg can reproduce.

  over ssh and in multi-user.target work good.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1985887/+subscriptions