I did read some threads / bugs.
>From what I can see so far, it doesn't relate to swap because stressors will 
>fill all memory / swap.

Although it's a stress test, I though if user has many tabs on browser
will eventually meet this issue.

>From what systemd-oomd current design, it will kill the process if
memory pressure over 50% (or 60 or configured percentage) over 20
seconds (or configured settings).

Thus, the current behavior is by design.
However, it leads bad experience.

Since most of user processes will be counted into gnome, then gnome will
frequently be killed if user launches heavy application.

I'm think about if expect a process can not use 5.60% memory is a
correct expectation.

There are many reports from upstream or other distributions to complaint
about it. or enhance it to have a notification before killing.

We could check why it won't happen in Xorg first.

** Also affects: oem-priority
   Importance: Undecided
       Status: New

** Summary changed:

- systemd kills gnome-shell or gnome-terminal if gnome in Wayland
+ systemd kills gnome-shell or gnome-terminal if gnome is in Wayland mode

** Tags added: oem-priority wayland

** Changed in: oem-priority
   Importance: Undecided => High

** Changed in: oem-priority
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1985887

Title:
  systemd kills gnome-shell or gnome-terminal if gnome is in Wayland
  mode

Status in OEM Priority Project:
  Confirmed
Status in systemd package in Ubuntu:
  New

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"
  3. Terminal or Gnome-shell will be killed by systemd-oomd

  It's because all stressors are under same cgroup.

  So far, it only happen in Wayland.

  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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to