[Bug 1985887] Re: systemd kills gnome-shell or gnome-terminal if gnome-terminal uses much memory (50% over 20s)
Daniel Johnson
1985887 at bugs.launchpad.net
Mon Oct 17 15:10:54 UTC 2022
Yesterday's copies did not trigger systemd-oomd, but one of them did
cause systemd-journald to timeout and restart.
Oct 16 14:00:07 Boromir systemd[1]: systemd-journald.service: Watchdog timeout (limit 3min)!
Oct 16 14:00:07 Boromir systemd[1]: systemd-journald.service: Killing process 578 (systemd-journal) with signal SIGABRT.
--
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
More information about the foundations-bugs
mailing list