Launchpad has imported 30 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=1941170.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2021-03-20T15:49:58+00:00 isaac.bernadus wrote: Description of problem: Systemd-oomd is very aggressive when it comes to memory management. In fedora 33 I've been able to run quite a few apps without a problem but in fedora 34, the apps get killed way too quickly. Here's an example of atom getting killed by systemd-oomd: Mar 20 22:18:34 x505za systemd-oomd[1020]: Memory pressure for /user.slice/user-1000.slice/user@1000.service is greater than 10 for more than 10 seconds and there was reclaim activity Mar 20 22:18:34 x505za systemd[1604]: app-gnome-atom-11930.scope: systemd-oomd killed 47 process(es) in this unit. Mar 20 22:18:36 x505za systemd[1604]: app-gnome-atom-11930.scope: Deactivated successfully. Mar 20 22:18:36 x505za systemd[1604]: app-gnome-atom-11930.scope: Consumed 7.557s CPU time This event is triggered when around 70-80% of my memory is filled up despite still having space in swap. Version-Release number of selected component (if applicable): systemd 248 (v248~rc4-1.fc34) How reproducible: Always Steps to Reproduce: 1. Load up a bunch of apps to fill up memory 2. Wait for systemd-oomd to trigger reclaim activity 3. Actual results: Apps get killed very quickly Expected results: Apps to run normally until memory and swap is almost full Additional info: System Specs: Ryzen 3 2200u 4GB RAM Kernel 5.11.7-300.fc34.x86_64 Reply at: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1972159/comments/0 ------------------------------------------------------------------------ On 2021-03-20T16:44:30+00:00 isaac.bernadus wrote: Seems like if the memory gets filled fast enough, systemd will even decide to kill Gnome Reply at: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1972159/comments/1 ------------------------------------------------------------------------ On 2021-03-23T14:59:38+00:00 red wrote: Same problem here. The fedora defaults are too aggressive. They make systemd-oomd very trigger-happy (ManagedOOMMemoryPressureLimit=10% for 10 seconds) With 4GB and zram, you can barely use anything. With 2GB it is a task- massacre all the time. The defaults suggested in the manual (60% & 30s) still prevent excessive spinning while working way more predictably. Reply at: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1972159/comments/2 ------------------------------------------------------------------------ On 2021-03-24T22:59:27+00:00 iolo wrote: I've noticed this too while testing Fedora Workstation 34 this week. I'll leave Netbeans or Brave running to go do something else, and I've got maybe about 4 GB of free RAM out of 8 GB total at that point. Then, some time later, I will try to go back to Netbeans or Brave, or whatever it is, only to find that it's been killed. I've never had anything like this happen before. Reply at: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1972159/comments/3 ------------------------------------------------------------------------ On 2021-03-25T07:12:19+00:00 the.anitazha wrote: I will work on updating the pressure defaults now that the test week results have come in. I agree that the defaults are a bit aggressive, but that's what the test week and beta was meant to iron out. Reply at: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1972159/comments/4 ------------------------------------------------------------------------ On 2021-03-30T09:04:29+00:00 the.anitazha wrote: I've submitted https://src.fedoraproject.org/rpms/systemd/pull- request/58# to bump pressure defaults to 50% for 20s. Hopefully these more conservative values will perform better for most people. Reply at: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1972159/comments/5 ------------------------------------------------------------------------ On 2021-03-31T09:18:33+00:00 updates wrote: FEDORA-2021-8595b30af3 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-8595b30af3 Reply at: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1972159/comments/6 ------------------------------------------------------------------------ On 2021-04-01T02:04:06+00:00 updates wrote: FEDORA-2021-8595b30af3 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-8595b30af3` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-8595b30af3 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. Reply at: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1972159/comments/7 ------------------------------------------------------------------------ On 2021-04-03T01:28:14+00:00 updates wrote: FEDORA-2021-8595b30af3 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report. Reply at: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1972159/comments/8 ------------------------------------------------------------------------ On 2021-04-07T14:20:40+00:00 mikhail.v.gavrilov wrote: Created attachment 1769904 htop Today oomd again killed my container. $ cat /usr/lib/systemd/oomd.conf.d/10-oomd-defaults.conf [OOM] DefaultMemoryPressureDurationSec=20s $ cat /usr/lib/systemd/system/user@.service.d/10-oomd-user-service-defaults.conf [Service] ManagedOOMMemoryPressure=kill ManagedOOMMemoryPressureLimit=50% Reply at: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1972159/comments/9 ------------------------------------------------------------------------ On 2021-04-07T14:21:13+00:00 mikhail.v.gavrilov wrote: Created attachment 1769916 system log Reply at: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1972159/comments/10 ------------------------------------------------------------------------ On 2021-04-07T14:33:13+00:00 mikhail.v.gavrilov wrote: Created attachment 1769918 system log Reply at: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1972159/comments/11 ------------------------------------------------------------------------ On 2021-04-08T22:42:10+00:00 the.anitazha wrote: @Mikhail Was the system responsive and performing well at 54% pressure on the user service cgroup? Also can you try stopping systemd-oomd (sudo systemctl stop systemd-oomd) and recording what the highest tolerable pressure value was from `/sys/fs/cgroup/user.slice/user-$UID.slice/user@$UID.service/memory.pressure` while your container is running? We can't control for all workloads but it's worthwhile to see what pressure is tolerable or not. Reply at: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1972159/comments/12 ------------------------------------------------------------------------ On 2021-09-07T19:56:26+00:00 mikhail.v.gavrilov wrote: (In reply to Anita Zhang from comment #12) > @Mikhail Was the system responsive and performing well at 54% pressure on > the user service cgroup? Also can you try stopping systemd-oomd (sudo > systemctl stop systemd-oomd) and recording what the highest tolerable > pressure value was from > `/sys/fs/cgroup/user.slice/user-$UID.slice/user@$UID.service/memory. > pressure` while your container is running? We can't control for all > workloads but it's worthwhile to see what pressure is tolerable or not. $ cat /sys/fs/cgroup/user.slice/user-$UID.slice/user@$UID.service/memory.pressure some avg10=0.00 avg60=0.00 avg300=0.13 total=1698253169 full avg10=0.00 avg60=0.00 avg300=0.11 total=1515028054 $ journalctl -b -u systemd-oomd --no-pager -- Journal begins at Thu 2021-07-29 17:02:00 +05, ends at Wed 2021-09-08 00:51:09 +05. -- Sep 04 03:16:03 primary-ws systemd[1]: Starting Userspace Out-Of-Memory (OOM) Killer... Sep 04 03:16:03 primary-ws systemd[1]: Started Userspace Out-Of-Memory (OOM) Killer. Sep 08 00:23:23 primary-ws systemd-oomd[1552]: Killed /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-887e6f17-fa6d-44cd-aa80-798d5c0c71ce.scope due to memory pressure for /user.slice/user-1000.slice/user@1000.service being 52.46% > 50.00% for > 20s with reclaim activity Reply at: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1972159/comments/13 ------------------------------------------------------------------------ On 2021-09-07T19:58:06+00:00 mikhail.v.gavrilov wrote: ^^^ This is F36 and systemd oomd still killing my terminal tabs. Reply at: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1972159/comments/14 ------------------------------------------------------------------------ On 2021-09-13T17:28:18+00:00 the.anitazha wrote: (In reply to Mikhail from comment #13) > $ journalctl -b -u systemd-oomd --no-pager > -- Journal begins at Thu 2021-07-29 17:02:00 +05, ends at Wed 2021-09-08 > 00:51:09 +05. -- > Sep 04 03:16:03 primary-ws systemd[1]: Starting Userspace Out-Of-Memory > (OOM) Killer... > Sep 04 03:16:03 primary-ws systemd[1]: Started Userspace Out-Of-Memory (OOM) > Killer. > Sep 08 00:23:23 primary-ws systemd-oomd[1552]: Killed > /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome. > Terminal.slice/vte-spawn-887e6f17-fa6d-44cd-aa80-798d5c0c71ce.scope due to > memory pressure for /user.slice/user-1000.slice/user@1000.service being > 52.46% > 50.00% for > 20s with reclaim activity You're pretty close to the default limits set up for Fedora so if you're fine with the added pressure you may want to try bumping them for your system with an override like so: $ cat /etc/systemd/system/user@.service.d/99-oomd-override.conf [Service] ManagedOOMMemoryPressureLimit=65% $ sudo systemctl daemon-reload $ oomctl # check if new limit was applied The default values will likely be reworked once https://github.com/systemd/systemd/pull/20690 is merged. This will allow setting more tuned pressure values on slices within a user session rather than relying on one value for all of user@UID.service. Reply at: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1972159/comments/15 ------------------------------------------------------------------------ On 2021-09-15T08:02:02+00:00 mikhail.v.gavrilov wrote: (In reply to Anita Zhang from comment #15) > > You're pretty close to the default limits set up for Fedora so if you're > fine with the added pressure you may want to try bumping them for your > system with an override like so: > > $ cat /etc/systemd/system/user@.service.d/99-oomd-override.conf Directory `user@.service.d` is absent on my system. $ ls /etc/systemd/system/user@.service.d ls: cannot access '/etc/systemd/system/user@.service.d': No such file or directory > [Service] > ManagedOOMMemoryPressureLimit=65% > $ sudo systemctl daemon-reload > $ oomctl # check if new limit was applied > > The default values will likely be reworked once > https://github.com/systemd/systemd/pull/20690 is merged. This will allow > setting more tuned pressure values on slices within a user session rather > than relying on one value for all of user@UID.service. As I am understand by default PressureLimit should be 50% $ cat /usr/lib/systemd/oomd.conf.d/10-oomd-defaults.conf [OOM] DefaultMemoryPressureDurationSec=20s $ cat /usr/lib/systemd/system/user@.service.d/10-oomd-user-service-defaults.conf [Service] ManagedOOMMemoryPressure=kill ManagedOOMMemoryPressureLimit=50% But oomctl show 60%, why? $ oomctl Dry Run: no Swap Used Limit: 90.00% Default Memory Pressure Limit: 60.00% Default Memory Pressure Duration: 20s System Context: Memory: Used: 55.3G Total: 62.6G Swap: Used: 104.5M Total: 63.9G Swap Monitored CGroups: Path: / Swap Usage: (see System Context) Memory Pressure Monitored CGroups: Path: /user.slice/user-1000.slice/user@1000.service Memory Pressure Limit: 50.00% Pressure: Avg10: 0.00 Avg60: 0.00 Avg300: 0.00 Total: 14s Current Memory Usage: 49.6G Memory Min: 250.0M Memory Low: 0B Pgscan: 85039860 Last Pgscan: 85039860 Reply at: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1972159/comments/16 ------------------------------------------------------------------------ On 2021-09-16T18:45:28+00:00 the.anitazha wrote: You(In reply to Mikhail from comment #16) > (In reply to Anita Zhang from comment #15) > Directory `user@.service.d` is absent on my system. You need to make it. Directories under /etc/systemd/system are managed by the system maintainer. > As I am understand by default PressureLimit should be 50% > > But oomctl show 60%, why? > > $ oomctl > Dry Run: no > Swap Used Limit: 90.00% > Default Memory Pressure Limit: 60.00% > Default Memory Pressure Duration: 20s > System Context: > Memory: Used: 55.3G Total: 62.6G > Swap: Used: 104.5M Total: 63.9G > Swap Monitored CGroups: > Path: / > Swap Usage: (see System Context) > Memory Pressure Monitored CGroups: > Path: /user.slice/user-1000.slice/user@1000.service > Memory Pressure Limit: 50.00% > Pressure: Avg10: 0.00 Avg60: 0.00 Avg300: 0.00 Total: 14s > Current Memory Usage: 49.6G > Memory Min: 250.0M > Memory Low: 0B > Pgscan: 85039860 > Last Pgscan: 85039860 Default memory pressure limit is 60% meaning if the unit doesn't override it, it will use 60%. But here since we ship a config for user@.service, the memory pressure limit is overridden to be 50% (it has it in the output above the "Pressure" line). Reply at: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1972159/comments/17 ------------------------------------------------------------------------ On 2021-11-12T14:57:19+00:00 mikhail.v.gavrilov wrote: > You're pretty close to the default limits set up for Fedora so if you're fine with the added pressure you may want to try bumping them for your system with an override like so ManagedOOMMemoryPressureLimit=65% did't helps :( $ journalctl -b -u systemd-oomd --no-pager -- Journal begins at Thu 2021-10-07 03:47:38 +05, ends at Fri 2021-11-12 19:54:14 +05. -- Nov 12 14:42:28 primary-ws systemd[1]: Starting Userspace Out-Of-Memory (OOM) Killer... Nov 12 14:42:28 primary-ws systemd[1]: Started Userspace Out-Of-Memory (OOM) Killer. Nov 12 17:50:48 primary-ws systemd-oomd[1172]: Killed /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-f92b7041-15da-41fb-8076-8221774567da.scope due to memory pressure for /user.slice/user-1000.slice/user@1000.service being 65.70% > 65.00% for > 20s with reclaim activity $ cat /sys/fs/cgroup/user.slice/user-$UID.slice/user@$UID.service/memory.pressure some avg10=3.68 avg60=31.49 avg300=25.59 total=424288160 full avg10=3.59 avg60=29.41 avg300=23.58 total=390639367 $ oomctl Dry Run: no Swap Used Limit: 90.00% Default Memory Pressure Limit: 60.00% Default Memory Pressure Duration: 20s System Context: Memory: Used: 60.4G Total: 62.6G Swap: Used: 16.5G Total: 71.9G Swap Monitored CGroups: Path: / Swap Usage: (see System Context) Memory Pressure Monitored CGroups: Path: /user.slice/user-1000.slice/user@1000.service Memory Pressure Limit: 65.00% Pressure: Avg10: 2.11 Avg60: 26.64 Avg300: 23.10 Total: 6min 30s Current Memory Usage: 25.5G Memory Min: 250.0M Memory Low: 0B Pgscan: 36702397 Last Pgscan: 36690917 Reply at: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1972159/comments/18 ------------------------------------------------------------------------ On 2022-04-14T11:46:24+00:00 mohd.akram wrote: How do I disable this completely? It's constantly killing apps despite plenty of RAM and swap space available. I do `sudo systemctl disable --now systemd-oomd.service` and it comes back when I restart. I don't want to use any userspace OOM killer. Reply at: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1972159/comments/19 ------------------------------------------------------------------------ On 2022-04-14T13:09:35+00:00 red wrote: (In reply to Mohamed Akram from comment #19) > How do I disable this completely? You can disable it completely with "systemctl mask systemd-oomd" (Masked services won't start even if you launch them manually.) Reply at: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1972159/comments/20 ------------------------------------------------------------------------ On 2022-04-14T17:33:26+00:00 the.anitazha wrote: (In reply to Mohamed Akram from comment #19) > It's constantly killing apps despite plenty of RAM and swap space available. Hey this sounds like a legit bug? Do you still have the logs from this event? They should be visible in the journal by doing `journalctl -u systemd-oomd -g Killed` Reply at: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1972159/comments/21 ------------------------------------------------------------------------ On 2022-05-31T04:57:02+00:00 mail wrote: Just wanted to chime in that I've had systemd-oomd kill my gnome shell four times in past two months on my current install of F35 (leading to a pretty jarring experience). I'm a pretty lay Linux user, will try to attach logs, let me know if anything else is helpful. Reply at: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1972159/comments/34 ------------------------------------------------------------------------ On 2022-05-31T04:59:38+00:00 mail wrote: Created attachment 1885395 journalctl -- oomd kills Reply at: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1972159/comments/35 ------------------------------------------------------------------------ On 2022-06-01T16:15:44+00:00 bugzilla wrote: >Mar 25 19:00:46 fedora systemd-oomd[1612]: Killed /user.slice/user-1000.slice/user@1000.service/session.slice/org.gnome.Shell@wayland.service due to memory used (16360116224) / total (16541884416) and swap used (7752622080) / total (8589930496) being more than 90.00% That something is being killed off at 90% swap usage makes sense, but not GNOME Shell. That's exchanging one big problem for another big problem, I'm not sure we can ever consider killing the desktop itself as a solution to the swap perf problem. And it makes me wonder if the only thing we can do is ensure resource control limits everything well enough that the user has the ability to choose what program needs to get killed off rather than doing it for them? As in, I'm wondering if oomd really should only be killing the most obvious candidates, and actually permit the less obvious candidates while still constraining the resources they can use to like 90% or whatever allows the shell+terminal to remain responsive enough (i.e. not perfect) such that the user doesn't reach for the power button. But instead reaches for top or systemd-cgtop to find out what's hogging resources, and decides whether to clobber it or not? Reply at: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1972159/comments/36 ------------------------------------------------------------------------ On 2022-06-01T18:31:57+00:00 mail wrote: I agree. I might add though (and this is my first time on linux forums, so I'm not sure how this is generally addressed) that this problem can easily affect non-technical end users as well, which would likely not be comfortable with shell commands such as top or systemd-cgtop. In case it is helpful, I'll attach a screenshot of how macOS solves this problem through a GUI interface for force-quitting that includes current memory usage for each application. I think this is a nice way of empowering the user to make the decision. However, I could not find an existing linux/GNOME GUI that does something similar. In the meantime, perhaps improving the heuristics of the resource manager so core services like GNOME Shell are not killed would be helpful. And I think that so long as auto-killing is the active solution, it would be nice for any apps that are killed due to memory constraints for there to be a system alert informing the user as to this decision, since the event otherwise seems quite anomalous. Reply at: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1972159/comments/37 ------------------------------------------------------------------------ On 2022-06-01T18:33:07+00:00 mail wrote: Created attachment 1885855 macos force quit GUI screenshot Reply at: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1972159/comments/38 ------------------------------------------------------------------------ On 2022-06-04T17:17:10+00:00 burkesamuel wrote: Created attachment 1886712 journalctl -u systemd-oomd -g Killed | grep -v Boot My daughter is using Fedora 35 with Cinnamon Desktop and has been complaining about randomly being logged out. We'll see how things go with systemd-oomd disabled/masked. Reply at: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1972159/comments/39 ------------------------------------------------------------------------ On 2022-12-22T20:51:29+00:00 bryanhoop wrote: I'm running into this issue, seemingly with plenty of RAM/swap available when running btrfs commands. btrbk and btrfs-progs commands are killed by systemd-oomd because they exceed the 50% memory pressure threshold for system.slice set in /usr/lib/systemd/system/system.slice.d/10-oomd- per-slice-defaults.conf. Here's some logging output: Dec 21 16:39:11 workstation systemd-oomd[1779]: Considered 74 cgroups for killing, top candidates were: Dec 21 13:49:51 workstation systemd[1]: btrbk.service: systemd-oomd killed 5 process(es) in this unit. Dec 21 13:49:51 workstation systemd-oomd[1779]: Killed /system.slice/btrbk.service due to memory pressure for /system.slice being 56.47% > 50.00% for > 20s with reclaim activity Dec 21 13:49:51 workstation systemd-oomd[1779]: Last Pgscan: 1411 Dec 21 13:49:51 workstation systemd-oomd[1779]: Pgscan: 1411 Dec 21 13:49:51 workstation systemd-oomd[1779]: Memory Low: 0B Dec 21 13:49:51 workstation systemd-oomd[1779]: Memory Min: 0B Dec 21 13:49:51 workstation systemd-oomd[1779]: Current Memory Usage: 9.0M Dec 21 13:49:51 workstation systemd-oomd[1779]: Pressure: Avg10: 0.00 Avg60: 0.00 Avg300: 0.00 Total: 0 Dec 21 13:49:51 workstation systemd-oomd[1779]: Memory Pressure Limit: 0.00% Dec 21 13:49:51 workstation systemd-oomd[1779]: Path: /system.slice/pcscd.service Dec 21 13:49:51 workstation systemd-oomd[1779]: Last Pgscan: 3337 Dec 21 13:49:51 workstation systemd-oomd[1779]: Pgscan: 3337 Dec 21 13:49:51 workstation systemd-oomd[1779]: Memory Low: 0B Dec 21 13:49:51 workstation systemd-oomd[1779]: Memory Min: 0B Dec 21 13:49:51 workstation systemd-oomd[1779]: Current Memory Usage: 12.8M Dec 21 13:49:51 workstation systemd-oomd[1779]: Pressure: Avg10: 0.00 Avg60: 0.00 Avg300: 0.00 Total: 1ms Dec 21 13:49:51 workstation systemd-oomd[1779]: Memory Pressure Limit: 0.00% Dec 21 13:49:51 workstation systemd-oomd[1779]: Path: /system.slice/geoclue.service Dec 21 13:49:51 workstation systemd-oomd[1779]: Last Pgscan: 12100 Dec 21 13:49:51 workstation systemd-oomd[1779]: Pgscan: 12100 Dec 21 13:49:51 workstation systemd-oomd[1779]: Memory Low: 0B Dec 21 13:49:51 workstation systemd-oomd[1779]: Memory Min: 0B Dec 21 13:49:51 workstation systemd-oomd[1779]: Current Memory Usage: 16.8M Dec 21 13:49:51 workstation systemd-oomd[1779]: Pressure: Avg10: 0.00 Avg60: 0.00 Avg300: 0.00 Total: 49us Dec 21 13:49:51 workstation systemd-oomd[1779]: Memory Pressure Limit: 0.00% Dec 21 13:49:51 workstation systemd-oomd[1779]: Path: /system.slice/udisks2.service Dec 21 13:49:51 workstation systemd-oomd[1779]: Last Pgscan: 10448 Dec 21 13:49:51 workstation systemd-oomd[1779]: Pgscan: 10448 Dec 21 13:49:51 workstation systemd-oomd[1779]: Memory Low: 0B Dec 21 13:49:51 workstation systemd-oomd[1779]: Memory Min: 0B Dec 21 13:49:51 workstation systemd-oomd[1779]: Current Memory Usage: 18.5M Dec 21 13:49:51 workstation systemd-oomd[1779]: Pressure: Avg10: 0.00 Avg60: 0.00 Avg300: 0.00 Total: 0 Dec 21 13:49:51 workstation systemd-oomd[1779]: Memory Pressure Limit: 0.00% Dec 21 13:49:51 workstation systemd-oomd[1779]: Path: /system.slice/firewalld.service Dec 21 13:49:51 workstation systemd-oomd[1779]: Last Pgscan: 4587 Dec 21 13:49:51 workstation systemd-oomd[1779]: Pgscan: 4587 Dec 21 13:49:51 workstation systemd-oomd[1779]: Memory Low: 0B Dec 21 13:49:51 workstation systemd-oomd[1779]: Memory Min: 0B Dec 21 13:49:51 workstation systemd-oomd[1779]: Current Memory Usage: 22.7M Dec 21 13:49:51 workstation systemd-oomd[1779]: Pressure: Avg10: 0.00 Avg60: 0.00 Avg300: 0.00 Total: 767us Dec 21 13:49:51 workstation systemd-oomd[1779]: Memory Pressure Limit: 0.00% Dec 21 13:49:51 workstation systemd-oomd[1779]: Path: /system.slice/sssd-kcm.service Dec 21 13:49:51 workstation systemd-oomd[1779]: Last Pgscan: 15997 Dec 21 13:49:51 workstation systemd-oomd[1779]: Pgscan: 15997 Dec 21 13:49:51 workstation systemd-oomd[1779]: Memory Low: 0B Dec 21 13:49:51 workstation systemd-oomd[1779]: Memory Min: 0B Dec 21 13:49:51 workstation systemd-oomd[1779]: Current Memory Usage: 25.7M Dec 21 13:49:51 workstation systemd-oomd[1779]: Pressure: Avg10: 0.00 Avg60: 0.00 Avg300: 0.00 Total: 6ms Dec 21 13:49:51 workstation systemd-oomd[1779]: Memory Pressure Limit: 0.00% Dec 21 13:49:51 workstation systemd-oomd[1779]: Path: /system.slice/libvirtd.service Dec 21 13:49:51 workstation systemd-oomd[1779]: Last Pgscan: 14820 Dec 21 13:49:51 workstation systemd-oomd[1779]: Pgscan: 14820 Dec 21 13:49:51 workstation systemd-oomd[1779]: Memory Low: 0B Dec 21 13:49:51 workstation systemd-oomd[1779]: Memory Min: 0B Dec 21 13:49:51 workstation systemd-oomd[1779]: Current Memory Usage: 30.8M Dec 21 13:49:51 workstation systemd-oomd[1779]: Pressure: Avg10: 0.00 Avg60: 0.00 Avg300: 0.00 Total: 45ms Dec 21 13:49:51 workstation systemd-oomd[1779]: Memory Pressure Limit: 0.00% Dec 21 13:49:51 workstation systemd-oomd[1779]: Path: /system.slice/polkit.service Dec 21 13:49:51 workstation systemd-oomd[1779]: Last Pgscan: 20593 Dec 21 13:49:51 workstation systemd-oomd[1779]: Pgscan: 20593 Dec 21 13:49:51 workstation systemd-oomd[1779]: Memory Low: 0B Dec 21 13:49:51 workstation systemd-oomd[1779]: Memory Min: 0B Dec 21 13:49:51 workstation systemd-oomd[1779]: Current Memory Usage: 32.0M Dec 21 13:49:51 workstation systemd-oomd[1779]: Pressure: Avg10: 0.00 Avg60: 0.00 Avg300: 0.00 Total: 2ms Dec 21 13:49:51 workstation systemd-oomd[1779]: Memory Pressure Limit: 0.00% Dec 21 13:49:51 workstation systemd-oomd[1779]: Path: /system.slice/tailscaled.service Dec 21 13:49:51 workstation systemd-oomd[1779]: Last Pgscan: 280813 Dec 21 13:49:51 workstation systemd-oomd[1779]: Pgscan: 280813 Dec 21 13:49:51 workstation systemd-oomd[1779]: Memory Low: 0B Dec 21 13:49:51 workstation systemd-oomd[1779]: Memory Min: 0B Dec 21 13:49:51 workstation systemd-oomd[1779]: Current Memory Usage: 101.4M Dec 21 13:49:51 workstation systemd-oomd[1779]: Pressure: Avg10: 0.00 Avg60: 0.00 Avg300: 0.00 Total: 214ms Dec 21 13:49:51 workstation systemd-oomd[1779]: Memory Pressure Limit: 0.00% Dec 21 13:49:51 workstation systemd-oomd[1779]: Path: /system.slice/systemd-journald.service Dec 21 13:49:51 workstation systemd-oomd[1779]: Last Pgscan: 123596614 Dec 21 13:49:51 workstation systemd-oomd[1779]: Pgscan: 123596614 Dec 21 13:49:51 workstation systemd-oomd[1779]: Memory Low: 0B Dec 21 13:49:51 workstation systemd-oomd[1779]: Memory Min: 0B Dec 21 13:49:51 workstation systemd-oomd[1779]: Current Memory Usage: 22.8G Dec 21 13:49:51 workstation systemd-oomd[1779]: Pressure: Avg10: 61.30 Avg60: 31.43 Avg300: 7.98 Total: 1min 1s Dec 21 13:49:51 workstation systemd-oomd[1779]: Memory Pressure Limit: 0.00% Dec 21 13:49:51 workstation systemd-oomd[1779]: Path: /system.slice/btrbk.service Dec 21 13:49:51 workstation systemd-oomd[1779]: Considered 74 cgroups for killing, top candidates were: Dec 21 12:58:39 workstation systemd[1822]: vte-spawn-72c022aa-5eab-40ce-afd3-59129e717177.scope: systemd-oomd killed 7 process(es) in this unit. Dec 21 12:48:28 workstation systemd-oomd[1779]: Killed /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-72c022aa-5eab-40ce-afd3-59129e717177.scope due to memory pressure for /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice being 59.94% > 50.00% for > 20s with reclaim activity Dec 21 12:48:28 workstation systemd-oomd[1779]: Last Pgscan: 6785 Dec 21 12:48:28 workstation systemd-oomd[1779]: Pgscan: 6785 Dec 21 12:48:28 workstation systemd-oomd[1779]: Memory Low: 0B Dec 21 12:48:28 workstation systemd-oomd[1779]: Memory Min: 0B Dec 21 12:48:28 workstation systemd-oomd[1779]: Current Memory Usage: 8.8M Dec 21 12:48:28 workstation systemd-oomd[1779]: Pressure: Avg10: 0.00 Avg60: 0.00 Avg300: 0.00 Total: 0 Dec 21 12:48:28 workstation systemd-oomd[1779]: Memory Pressure Limit: 0.00% Dec 21 12:48:28 workstation systemd-oomd[1779]: Path: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-a9f026a6-b6e7-4c0f-847d-95412169775d.scope Dec 21 12:48:28 workstation systemd-oomd[1779]: Last Pgscan: 1220 Dec 21 12:48:28 workstation systemd-oomd[1779]: Pgscan: 1220 Dec 21 12:48:28 workstation systemd-oomd[1779]: Memory Low: 0B Dec 21 12:48:28 workstation systemd-oomd[1779]: Memory Min: 0B Dec 21 12:48:28 workstation systemd-oomd[1779]: Current Memory Usage: 9.6M Dec 21 12:48:28 workstation systemd-oomd[1779]: Pressure: Avg10: 0.00 Avg60: 0.00 Avg300: 0.00 Total: 1s Dec 21 12:48:28 workstation systemd-oomd[1779]: Memory Pressure Limit: 0.00% Dec 21 12:48:28 workstation systemd-oomd[1779]: Path: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-4d89eced-3e3c-4736-850b-50388d11920a.scope Dec 21 12:48:28 workstation systemd-oomd[1779]: Last Pgscan: 2372 Dec 21 12:48:28 workstation systemd-oomd[1779]: Pgscan: 2372 Dec 21 12:48:28 workstation systemd-oomd[1779]: Memory Low: 0B Dec 21 12:48:28 workstation systemd-oomd[1779]: Memory Min: 0B Dec 21 12:48:28 workstation systemd-oomd[1779]: Current Memory Usage: 10.0M Dec 21 12:48:28 workstation systemd-oomd[1779]: Pressure: Avg10: 0.00 Avg60: 0.00 Avg300: 0.00 Total: 0 Dec 21 12:48:28 workstation systemd-oomd[1779]: Memory Pressure Limit: 0.00% Dec 21 12:48:28 workstation systemd-oomd[1779]: Path: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-ac54c0c6-540f-467f-b9b4-3153c68de2c7.scope Dec 21 12:48:28 workstation systemd-oomd[1779]: Last Pgscan: 19395 Dec 21 12:48:28 workstation systemd-oomd[1779]: Pgscan: 19395 Dec 21 12:48:28 workstation systemd-oomd[1779]: Memory Low: 0B Dec 21 12:48:28 workstation systemd-oomd[1779]: Memory Min: 0B Dec 21 12:48:28 workstation systemd-oomd[1779]: Current Memory Usage: 14.3M Dec 21 12:48:28 workstation systemd-oomd[1779]: Pressure: Avg10: 0.00 Avg60: 0.00 Avg300: 0.00 Total: 2ms Dec 21 12:48:28 workstation systemd-oomd[1779]: Memory Pressure Limit: 0.00% Dec 21 12:48:28 workstation systemd-oomd[1779]: Path: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-90678602-9682-4e48-a4b9-b5ddc7e1f85b.scope Dec 21 12:48:28 workstation systemd-oomd[1779]: Last Pgscan: 1027 Dec 21 12:48:28 workstation systemd-oomd[1779]: Pgscan: 1027 Dec 21 12:48:28 workstation systemd-oomd[1779]: Memory Low: 0B Dec 21 12:48:28 workstation systemd-oomd[1779]: Memory Min: 0B Dec 21 12:48:28 workstation systemd-oomd[1779]: Current Memory Usage: 14.3M Dec 21 12:48:28 workstation systemd-oomd[1779]: Pressure: Avg10: 0.00 Avg60: 0.00 Avg300: 0.00 Total: 33ms Dec 21 12:48:28 workstation systemd-oomd[1779]: Memory Pressure Limit: 0.00% Dec 21 12:48:28 workstation systemd-oomd[1779]: Path: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-170330ec-5d4d-48ea-a186-cdb97b717340.scope Dec 21 12:48:28 workstation systemd-oomd[1779]: Last Pgscan: 19760 Dec 21 12:48:28 workstation systemd-oomd[1779]: Pgscan: 19760 Dec 21 12:48:28 workstation systemd-oomd[1779]: Memory Low: 0B Dec 21 12:48:28 workstation systemd-oomd[1779]: Memory Min: 0B Dec 21 12:48:28 workstation systemd-oomd[1779]: Current Memory Usage: 40.1M Dec 21 12:48:28 workstation systemd-oomd[1779]: Pressure: Avg10: 0.00 Avg60: 0.00 Avg300: 0.00 Total: 44us Dec 21 12:48:28 workstation systemd-oomd[1779]: Memory Pressure Limit: 0.00% Dec 21 12:48:28 workstation systemd-oomd[1779]: Path: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-f5d8af10-7b4b-4b33-a0e1-93226c643c92.scope Dec 21 12:48:28 workstation systemd-oomd[1779]: Last Pgscan: 11777 Dec 21 12:48:28 workstation systemd-oomd[1779]: Pgscan: 11778 Dec 21 12:48:28 workstation systemd-oomd[1779]: Memory Low: 0B Dec 21 12:48:28 workstation systemd-oomd[1779]: Memory Min: 0B Dec 21 12:48:28 workstation systemd-oomd[1779]: Current Memory Usage: 66.3M Dec 21 12:48:28 workstation systemd-oomd[1779]: Pressure: Avg10: 0.00 Avg60: 0.00 Avg300: 0.00 Total: 3ms Dec 21 12:48:28 workstation systemd-oomd[1779]: Memory Pressure Limit: 0.00% Dec 21 12:48:28 workstation systemd-oomd[1779]: Path: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/gnome-terminal-server.service Dec 21 12:48:28 workstation systemd-oomd[1779]: Last Pgscan: 4496083 Dec 21 12:48:28 workstation systemd-oomd[1779]: Pgscan: 4496089 Dec 21 12:48:28 workstation systemd-oomd[1779]: Memory Low: 0B Dec 21 12:48:28 workstation systemd-oomd[1779]: Memory Min: 0B Dec 21 12:48:28 workstation systemd-oomd[1779]: Current Memory Usage: 33.1M Dec 21 12:48:28 workstation systemd-oomd[1779]: Pressure: Avg10: 0.00 Avg60: 0.00 Avg300: 0.00 Total: 0 Dec 21 12:48:28 workstation systemd-oomd[1779]: Memory Pressure Limit: 0.00% Dec 21 12:48:28 workstation systemd-oomd[1779]: Path: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-ef755045-3c70-4474-af12-0f7e5308b31f.scope Dec 21 12:48:28 workstation systemd-oomd[1779]: Last Pgscan: 14812636 Dec 21 12:48:28 workstation systemd-oomd[1779]: Pgscan: 14812701 Dec 21 12:48:28 workstation systemd-oomd[1779]: Memory Low: 0B Dec 21 12:48:28 workstation systemd-oomd[1779]: Memory Min: 0B Dec 21 12:48:28 workstation systemd-oomd[1779]: Current Memory Usage: 238.1M Dec 21 12:48:28 workstation systemd-oomd[1779]: Pressure: Avg10: 0.00 Avg60: 0.00 Avg300: 0.00 Total: 6min 48s Dec 21 12:48:28 workstation systemd-oomd[1779]: Memory Pressure Limit: 0.00% Dec 21 12:48:28 workstation systemd-oomd[1779]: Path: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-9be7cda0-e037-4900-9170-f2461461dc2e.scope Dec 21 12:48:28 workstation systemd-oomd[1779]: Last Pgscan: 1119658 Dec 21 12:48:28 workstation systemd-oomd[1779]: Pgscan: 1119839 Dec 21 12:48:28 workstation systemd-oomd[1779]: Memory Low: 0B Dec 21 12:48:28 workstation systemd-oomd[1779]: Memory Min: 0B Dec 21 12:48:28 workstation systemd-oomd[1779]: Current Memory Usage: 587.5M Dec 21 12:48:28 workstation systemd-oomd[1779]: Pressure: Avg10: 65.19 Avg60: 44.96 Avg300: 24.63 Total: 4min 1s Dec 21 12:48:28 workstation systemd-oomd[1779]: Memory Pressure Limit: 0.00% Dec 21 12:48:28 workstation systemd-oomd[1779]: Path: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-72c022aa-5eab-40ce-afd3-59129e717177.scope Dec 21 12:48:28 workstation systemd-oomd[1779]: Considered 12 cgroups for killing, top candidates were: Dec 21 12:46:28 workstation systemd[1822]: vte-spawn-72c022aa-5eab-40ce-afd3-59129e717177.scope: systemd-oomd killed 6 process(es) in this unit. Dec 21 12:46:28 workstation systemd-oomd[1779]: Killed /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-72c022aa-5eab-40ce-afd3-59129e717177.scope due to memory pressure for /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice being 86.76% > 50.00% for > 20s with reclaim activity Dec 21 12:46:28 workstation systemd-oomd[1779]: Last Pgscan: 6735 Dec 21 12:46:28 workstation systemd-oomd[1779]: Pgscan: 6735 Dec 21 12:46:28 workstation systemd-oomd[1779]: Memory Low: 0B Dec 21 12:46:28 workstation systemd-oomd[1779]: Memory Min: 0B Dec 21 12:46:28 workstation systemd-oomd[1779]: Current Memory Usage: 9.0M Dec 21 12:46:28 workstation systemd-oomd[1779]: Pressure: Avg10: 0.00 Avg60: 0.00 Avg300: 0.00 Total: 0 Dec 21 12:46:28 workstation systemd-oomd[1779]: Memory Pressure Limit: 0.00% Dec 21 12:46:28 workstation systemd-oomd[1779]: Path: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-a9f026a6-b6e7-4c0f-847d-95412169775d.scope Dec 21 12:46:28 workstation systemd-oomd[1779]: Last Pgscan: 1186 Dec 21 12:46:28 workstation systemd-oomd[1779]: Pgscan: 1186 Dec 21 12:46:28 workstation systemd-oomd[1779]: Memory Low: 0B Dec 21 12:46:28 workstation systemd-oomd[1779]: Memory Min: 0B Dec 21 12:46:28 workstation systemd-oomd[1779]: Current Memory Usage: 9.6M Dec 21 12:46:28 workstation systemd-oomd[1779]: Pressure: Avg10: 0.00 Avg60: 0.00 Avg300: 0.00 Total: 1s Dec 21 12:46:28 workstation systemd-oomd[1779]: Memory Pressure Limit: 0.00% Dec 21 12:46:28 workstation systemd-oomd[1779]: Path: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-4d89eced-3e3c-4736-850b-50388d11920a.scope Dec 21 12:46:28 workstation systemd-oomd[1779]: Last Pgscan: 2310 Dec 21 12:46:28 workstation systemd-oomd[1779]: Pgscan: 2310 Dec 21 12:46:28 workstation systemd-oomd[1779]: Memory Low: 0B Dec 21 12:46:28 workstation systemd-oomd[1779]: Memory Min: 0B Dec 21 12:46:28 workstation systemd-oomd[1779]: Current Memory Usage: 10.1M Dec 21 12:46:28 workstation systemd-oomd[1779]: Pressure: Avg10: 0.00 Avg60: 0.00 Avg300: 0.00 Total: 0 Dec 21 12:46:28 workstation systemd-oomd[1779]: Memory Pressure Limit: 0.00% Dec 21 12:46:28 workstation systemd-oomd[1779]: Path: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-ac54c0c6-540f-467f-b9b4-3153c68de2c7.scope Dec 21 12:46:28 workstation systemd-oomd[1779]: Last Pgscan: 11237 Dec 21 12:46:28 workstation systemd-oomd[1779]: Pgscan: 11237 Dec 21 12:46:28 workstation systemd-oomd[1779]: Memory Low: 0B Dec 21 12:46:28 workstation systemd-oomd[1779]: Memory Min: 0B Dec 21 12:46:28 workstation systemd-oomd[1779]: Current Memory Usage: 66.8M Dec 21 12:46:28 workstation systemd-oomd[1779]: Pressure: Avg10: 0.00 Avg60: 0.00 Avg300: 0.00 Total: 3ms Dec 21 12:46:28 workstation systemd-oomd[1779]: Memory Pressure Limit: 0.00% Dec 21 12:46:28 workstation systemd-oomd[1779]: Path: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/gnome-terminal-server.service Dec 21 12:46:28 workstation systemd-oomd[1779]: Last Pgscan: 871 Dec 21 12:46:28 workstation systemd-oomd[1779]: Pgscan: 872 Dec 21 12:46:28 workstation systemd-oomd[1779]: Memory Low: 0B Dec 21 12:46:28 workstation systemd-oomd[1779]: Memory Min: 0B Dec 21 12:46:28 workstation systemd-oomd[1779]: Current Memory Usage: 14.7M Dec 21 12:46:28 workstation systemd-oomd[1779]: Pressure: Avg10: 0.00 Avg60: 0.00 Avg300: 0.00 Total: 33ms Dec 21 12:46:28 workstation systemd-oomd[1779]: Memory Pressure Limit: 0.00% Dec 21 12:46:28 workstation systemd-oomd[1779]: Path: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-170330ec-5d4d-48ea-a186-cdb97b717340.scope Dec 21 12:46:28 workstation systemd-oomd[1779]: Last Pgscan: 19238 Dec 21 12:46:28 workstation systemd-oomd[1779]: Pgscan: 19239 Dec 21 12:46:28 workstation systemd-oomd[1779]: Memory Low: 0B Dec 21 12:46:28 workstation systemd-oomd[1779]: Memory Min: 0B Dec 21 12:46:28 workstation systemd-oomd[1779]: Current Memory Usage: 18.4M Dec 21 12:46:28 workstation systemd-oomd[1779]: Pressure: Avg10: 0.00 Avg60: 0.00 Avg300: 0.00 Total: 2ms Dec 21 12:46:28 workstation systemd-oomd[1779]: Memory Pressure Limit: 0.00% Dec 21 12:46:28 workstation systemd-oomd[1779]: Path: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-90678602-9682-4e48-a4b9-b5ddc7e1f85b.scope Dec 21 12:46:28 workstation systemd-oomd[1779]: Last Pgscan: 19427 Dec 21 12:46:28 workstation systemd-oomd[1779]: Pgscan: 19428 Dec 21 12:46:28 workstation systemd-oomd[1779]: Memory Low: 0B Dec 21 12:46:28 workstation systemd-oomd[1779]: Memory Min: 0B Dec 21 12:46:28 workstation systemd-oomd[1779]: Current Memory Usage: 40.4M Dec 21 12:46:28 workstation systemd-oomd[1779]: Pressure: Avg10: 0.00 Avg60: 0.00 Avg300: 0.00 Total: 44us Dec 21 12:46:28 workstation systemd-oomd[1779]: Memory Pressure Limit: 0.00% Dec 21 12:46:28 workstation systemd-oomd[1779]: Path: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-f5d8af10-7b4b-4b33-a0e1-93226c643c92.scope Dec 21 12:46:28 workstation systemd-oomd[1779]: Last Pgscan: 4494808 Dec 21 12:46:28 workstation systemd-oomd[1779]: Pgscan: 4494821 Dec 21 12:46:28 workstation systemd-oomd[1779]: Memory Low: 0B Dec 21 12:46:28 workstation systemd-oomd[1779]: Memory Min: 0B Dec 21 12:46:28 workstation systemd-oomd[1779]: Current Memory Usage: 38.4M Dec 21 12:46:28 workstation systemd-oomd[1779]: Pressure: Avg10: 0.00 Avg60: 0.00 Avg300: 0.00 Total: 0 Dec 21 12:46:28 workstation systemd-oomd[1779]: Memory Pressure Limit: 0.00% Dec 21 12:46:28 workstation systemd-oomd[1779]: Path: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-ef755045-3c70-4474-af12-0f7e5308b31f.scope Dec 21 12:46:28 workstation systemd-oomd[1779]: Last Pgscan: 14800650 Dec 21 12:46:28 workstation systemd-oomd[1779]: Pgscan: 14800747 Dec 21 12:46:28 workstation systemd-oomd[1779]: Memory Low: 0B Dec 21 12:46:28 workstation systemd-oomd[1779]: Memory Min: 0B Dec 21 12:46:28 workstation systemd-oomd[1779]: Current Memory Usage: 285.9M Dec 21 12:46:28 workstation systemd-oomd[1779]: Pressure: Avg10: 0.00 Avg60: 0.00 Avg300: 0.00 Total: 6min 48s Dec 21 12:46:28 workstation systemd-oomd[1779]: Memory Pressure Limit: 0.00% Dec 21 12:46:28 workstation systemd-oomd[1779]: Path: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-9be7cda0-e037-4900-9170-f2461461dc2e.scope Dec 21 12:46:28 workstation systemd-oomd[1779]: Last Pgscan: 1078348 Dec 21 12:46:28 workstation systemd-oomd[1779]: Pgscan: 1078704 Dec 21 12:46:28 workstation systemd-oomd[1779]: Memory Low: 0B Dec 21 12:46:28 workstation systemd-oomd[1779]: Memory Min: 0B Dec 21 12:46:28 workstation systemd-oomd[1779]: Current Memory Usage: 762.7M Dec 21 12:46:28 workstation systemd-oomd[1779]: Pressure: Avg10: 87.04 Avg60: 38.75 Avg300: 16.92 Total: 3min 14s Dec 21 12:46:28 workstation systemd-oomd[1779]: Memory Pressure Limit: 0.00% Dec 21 12:46:28 workstation systemd-oomd[1779]: Path: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-72c022aa-5eab-40ce-afd3-59129e717177.scope Dec 21 12:46:28 workstation systemd-oomd[1779]: Considered 12 cgroups for killing, top candidates were: Dec 20 08:40:06 workstation audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-oomd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Dec 20 08:40:06 workstation systemd[1]: Started systemd-oomd.service - Userspace Out-Of-Memory (OOM) Killer. Dec 20 08:40:06 workstation systemd[1]: Starting systemd-oomd.service - Userspace Out-Of-Memory (OOM) Killer... Dec 20 08:40:06 workstation systemd[1]: Listening on systemd-oomd.socket - Userspace Out-Of-Memory (OOM) Killer Socket. Dec 20 08:27:18 workstation systemd[1]: systemd-oomd.service: Consumed 40min 58.205s CPU time. Dec 20 08:27:18 workstation audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-oomd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Dec 20 08:27:18 workstation systemd[1]: Stopped systemd-oomd.service - Userspace Out-Of-Memory (OOM) Killer. Dec 20 08:27:18 workstation systemd[1]: systemd-oomd.service: Deactivated successfully. Dec 20 08:27:18 workstation systemd[1]: Stopping systemd-oomd.service - Userspace Out-Of-Memory (OOM) Killer... Dec 18 21:45:30 workstation systemd[8150]: vte-spawn-652212ca-a45c-4674-b5e8-0f4b70d334c0.scope: systemd-oomd killed 4 process(es) in this unit. Dec 18 21:43:34 workstation systemd-oomd[8105]: Killed /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-652212ca-a45c-4674-b5e8-0f4b70d334c0.scope due to memory pressure for /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice being 79.46% > 50.00% for > 20s with reclaim activity Dec 18 21:43:34 workstation systemd-oomd[8105]: Last Pgscan: 299974 Dec 18 21:43:34 workstation systemd-oomd[8105]: Pgscan: 299974 Dec 18 21:43:34 workstation systemd-oomd[8105]: Memory Low: 0B Dec 18 21:43:34 workstation systemd-oomd[8105]: Memory Min: 0B Dec 18 21:43:34 workstation systemd-oomd[8105]: Current Memory Usage: 1.2M Dec 18 21:43:34 workstation systemd-oomd[8105]: Pressure: Avg10: 0.00 Avg60: 0.00 Avg300: 0.00 Total: 28ms Dec 18 21:43:34 workstation systemd-oomd[8105]: Memory Pressure Limit: 0.00% Dec 18 21:43:34 workstation systemd-oomd[8105]: Path: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-a37c077d-1afc-457c-bb01-88981b643697.scope Dec 18 21:43:34 workstation systemd-oomd[8105]: Last Pgscan: 1256 Dec 18 21:43:34 workstation systemd-oomd[8105]: Pgscan: 1257 Dec 18 21:43:34 workstation systemd-oomd[8105]: Memory Low: 0B Dec 18 21:43:34 workstation systemd-oomd[8105]: Memory Min: 0B Dec 18 21:43:34 workstation systemd-oomd[8105]: Current Memory Usage: 9.8M Dec 18 21:43:34 workstation systemd-oomd[8105]: Pressure: Avg10: 0.00 Avg60: 0.00 Avg300: 0.00 Total: 0 Dec 18 21:43:34 workstation systemd-oomd[8105]: Memory Pressure Limit: 0.00% Dec 18 21:43:34 workstation systemd-oomd[8105]: Path: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-0b896f97-6a0a-4689-a5fd-0fb53c907d68.scope Dec 18 21:43:34 workstation systemd-oomd[8105]: Last Pgscan: 7207 Dec 18 21:43:34 workstation systemd-oomd[8105]: Pgscan: 7208 Dec 18 21:43:34 workstation systemd-oomd[8105]: Memory Low: 0B Dec 18 21:43:34 workstation systemd-oomd[8105]: Memory Min: 0B Dec 18 21:43:34 workstation systemd-oomd[8105]: Current Memory Usage: 11.7M Dec 18 21:43:34 workstation systemd-oomd[8105]: Pressure: Avg10: 0.00 Avg60: 0.00 Avg300: 0.00 Total: 3ms Dec 18 21:43:34 workstation systemd-oomd[8105]: Memory Pressure Limit: 0.00% Dec 18 21:43:34 workstation systemd-oomd[8105]: Path: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-7d146edc-ac5d-404a-a64d-a39cfa38ffeb.scope Dec 18 21:43:34 workstation systemd-oomd[8105]: Last Pgscan: 3041 Dec 18 21:43:34 workstation systemd-oomd[8105]: Pgscan: 3042 Dec 18 21:43:34 workstation systemd-oomd[8105]: Memory Low: 0B Dec 18 21:43:34 workstation systemd-oomd[8105]: Memory Min: 0B Dec 18 21:43:34 workstation systemd-oomd[8105]: Current Memory Usage: 13.2M Dec 18 21:43:34 workstation systemd-oomd[8105]: Pressure: Avg10: 0.00 Avg60: 0.00 Avg300: 0.00 Total: 98us Dec 18 21:43:34 workstation systemd-oomd[8105]: Memory Pressure Limit: 0.00% Dec 18 21:43:34 workstation systemd-oomd[8105]: Path: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-5ec2c910-9245-4735-830c-f3fc5a87de68.scope Dec 18 21:43:34 workstation systemd-oomd[8105]: Last Pgscan: 297496 Dec 18 21:43:34 workstation systemd-oomd[8105]: Pgscan: 297497 Dec 18 21:43:34 workstation systemd-oomd[8105]: Memory Low: 0B Dec 18 21:43:34 workstation systemd-oomd[8105]: Memory Min: 0B Dec 18 21:43:34 workstation systemd-oomd[8105]: Current Memory Usage: 22.6M Dec 18 21:43:34 workstation systemd-oomd[8105]: Pressure: Avg10: 0.00 Avg60: 0.00 Avg300: 0.00 Total: 8ms Dec 18 21:43:34 workstation systemd-oomd[8105]: Memory Pressure Limit: 0.00% Dec 18 21:43:34 workstation systemd-oomd[8105]: Path: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-55295c0c-f457-4b67-982c-575e55cf2551.scope Dec 18 21:43:34 workstation systemd-oomd[8105]: Last Pgscan: 72183 Dec 18 21:43:34 workstation systemd-oomd[8105]: Pgscan: 72190 Dec 18 21:43:34 workstation systemd-oomd[8105]: Memory Low: 0B Dec 18 21:43:34 workstation systemd-oomd[8105]: Memory Min: 0B Dec 18 21:43:34 workstation systemd-oomd[8105]: Current Memory Usage: 37.1M Dec 18 21:43:34 workstation systemd-oomd[8105]: Pressure: Avg10: 0.00 Avg60: 0.00 Avg300: 0.00 Total: 59ms Dec 18 21:43:34 workstation systemd-oomd[8105]: Memory Pressure Limit: 0.00% Dec 18 21:43:34 workstation systemd-oomd[8105]: Path: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/gnome-terminal-server.service Dec 18 21:43:34 workstation systemd-oomd[8105]: Last Pgscan: 10377672 Dec 18 21:43:34 workstation systemd-oomd[8105]: Pgscan: 10379088 Dec 18 21:43:34 workstation systemd-oomd[8105]: Memory Low: 0B Dec 18 21:43:34 workstation systemd-oomd[8105]: Memory Min: 0B Dec 18 21:43:34 workstation systemd-oomd[8105]: Current Memory Usage: 876.7M Dec 18 21:43:34 workstation systemd-oomd[8105]: Pressure: Avg10: 78.57 Avg60: 48.76 Avg300: 16.29 Total: 4min 6s Dec 18 21:43:34 workstation systemd-oomd[8105]: Memory Pressure Limit: 0.00% Dec 18 21:43:34 workstation systemd-oomd[8105]: Path: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-652212ca-a45c-4674-b5e8-0f4b70d334c0.scope Dec 18 21:43:34 workstation systemd-oomd[8105]: Considered 7 cgroups for killing, top candidates were: Dec 18 21:42:47 workstation systemd[8150]: vte-spawn-652212ca-a45c-4674-b5e8-0f4b70d334c0.scope: systemd-oomd killed 3 process(es) in this unit. Dec 18 21:42:47 workstation systemd-oomd[8105]: Killed /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-652212ca-a45c-4674-b5e8-0f4b70d334c0.scope due to memory pressure for /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice being 72.28% > 50.00% for > 20s with reclaim activity Dec 18 21:42:47 workstation systemd-oomd[8105]: Last Pgscan: 299974 Dec 18 21:42:47 workstation systemd-oomd[8105]: Pgscan: 299974 Dec 18 21:42:47 workstation systemd-oomd[8105]: Memory Low: 0B Dec 18 21:42:47 workstation systemd-oomd[8105]: Memory Min: 0B Dec 18 21:42:47 workstation systemd-oomd[8105]: Current Memory Usage: 1.2M Dec 18 21:42:47 workstation systemd-oomd[8105]: Pressure: Avg10: 0.00 Avg60: 0.00 Avg300: 0.00 Total: 28ms Dec 18 21:42:47 workstation systemd-oomd[8105]: Memory Pressure Limit: 0.00% Dec 18 21:42:47 workstation systemd-oomd[8105]: Path: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-a37c077d-1afc-457c-bb01-88981b643697.scope Dec 18 21:42:47 workstation systemd-oomd[8105]: Last Pgscan: 1181 Dec 18 21:42:47 workstation systemd-oomd[8105]: Pgscan: 1181 Dec 18 21:42:47 workstation systemd-oomd[8105]: Memory Low: 0B Dec 18 21:42:47 workstation systemd-oomd[8105]: Memory Min: 0B Dec 18 21:42:47 workstation systemd-oomd[8105]: Current Memory Usage: 9.8M Dec 18 21:42:47 workstation systemd-oomd[8105]: Pressure: Avg10: 0.00 Avg60: 0.00 Avg300: 0.00 Total: 0 Dec 18 21:42:47 workstation systemd-oomd[8105]: Memory Pressure Limit: 0.00% Dec 18 21:42:47 workstation systemd-oomd[8105]: Path: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-0b896f97-6a0a-4689-a5fd-0fb53c907d68.scope Dec 18 21:42:47 workstation systemd-oomd[8105]: Last Pgscan: 7178 Dec 18 21:42:47 workstation systemd-oomd[8105]: Pgscan: 7178 Dec 18 21:42:47 workstation systemd-oomd[8105]: Memory Low: 0B Dec 18 21:42:47 workstation systemd-oomd[8105]: Memory Min: 0B Dec 18 21:42:47 workstation systemd-oomd[8105]: Current Memory Usage: 11.8M Dec 18 21:42:47 workstation systemd-oomd[8105]: Pressure: Avg10: 0.00 Avg60: 0.00 Avg300: 0.00 Total: 3ms Dec 18 21:42:47 workstation systemd-oomd[8105]: Memory Pressure Limit: 0.00% Dec 18 21:42:47 workstation systemd-oomd[8105]: Path: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-7d146edc-ac5d-404a-a64d-a39cfa38ffeb.scope Dec 18 21:42:47 workstation systemd-oomd[8105]: Last Pgscan: 2966 Dec 18 21:42:47 workstation systemd-oomd[8105]: Pgscan: 2966 Dec 18 21:42:47 workstation systemd-oomd[8105]: Memory Low: 0B Dec 18 21:42:47 workstation systemd-oomd[8105]: Memory Min: 0B Dec 18 21:42:47 workstation systemd-oomd[8105]: Current Memory Usage: 13.2M Dec 18 21:42:47 workstation systemd-oomd[8105]: Pressure: Avg10: 0.00 Avg60: 0.00 Avg300: 0.00 Total: 98us Dec 18 21:42:47 workstation systemd-oomd[8105]: Memory Pressure Limit: 0.00% Dec 18 21:42:47 workstation systemd-oomd[8105]: Path: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-5ec2c910-9245-4735-830c-f3fc5a87de68.scope Dec 18 21:42:47 workstation systemd-oomd[8105]: Last Pgscan: 297421 Dec 18 21:42:47 workstation systemd-oomd[8105]: Pgscan: 297421 Dec 18 21:42:47 workstation systemd-oomd[8105]: Memory Low: 0B Dec 18 21:42:47 workstation systemd-oomd[8105]: Memory Min: 0B Dec 18 21:42:47 workstation systemd-oomd[8105]: Current Memory Usage: 22.9M Dec 18 21:42:47 workstation systemd-oomd[8105]: Pressure: Avg10: 0.00 Avg60: 0.00 Avg300: 0.00 Total: 8ms Dec 18 21:42:47 workstation systemd-oomd[8105]: Memory Pressure Limit: 0.00% Dec 18 21:42:47 workstation systemd-oomd[8105]: Path: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-55295c0c-f457-4b67-982c-575e55cf2551.scope Dec 18 21:42:47 workstation systemd-oomd[8105]: Last Pgscan: 71920 Dec 18 21:42:47 workstation systemd-oomd[8105]: Pgscan: 71921 Dec 18 21:42:47 workstation systemd-oomd[8105]: Memory Low: 0B Dec 18 21:42:47 workstation systemd-oomd[8105]: Memory Min: 0B Dec 18 21:42:47 workstation systemd-oomd[8105]: Current Memory Usage: 53.8M Dec 18 21:42:47 workstation systemd-oomd[8105]: Pressure: Avg10: 0.00 Avg60: 0.00 Avg300: 0.00 Total: 59ms Dec 18 21:42:47 workstation systemd-oomd[8105]: Memory Pressure Limit: 0.00% Dec 18 21:42:47 workstation systemd-oomd[8105]: Path: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/gnome-terminal-server.service Dec 18 21:42:47 workstation systemd-oomd[8105]: Last Pgscan: 10325032 Dec 18 21:42:47 workstation systemd-oomd[8105]: Pgscan: 10326435 Dec 18 21:42:47 workstation systemd-oomd[8105]: Memory Low: 0B Dec 18 21:42:47 workstation systemd-oomd[8105]: Memory Min: 0B Dec 18 21:42:47 workstation systemd-oomd[8105]: Current Memory Usage: 1.0G Dec 18 21:42:47 workstation systemd-oomd[8105]: Pressure: Avg10: 72.90 Avg60: 36.61 Avg300: 9.84 Total: 3min 40s Dec 18 21:42:47 workstation systemd-oomd[8105]: Memory Pressure Limit: 0.00% Dec 18 21:42:47 workstation systemd-oomd[8105]: Path: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-652212ca-a45c-4674-b5e8-0f4b70d334c0.scope Dec 18 21:42:47 workstation systemd-oomd[8105]: Considered 7 cgroups for killing, top candidates were: Reply at: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1972159/comments/60 ------------------------------------------------------------------------ On 2023-01-20T18:44:52+00:00 rkudyba wrote: Still on Fedora 36 from a MobaXterm client using ssh -X: systemd[1]: systemd-oomd.service - Userspace Out-Of-Memory (OOM) Killer was skipped because of a failed condition check (ConditionControlGroupController=v2). Default settings, systemd-oomd-defaults-250.9-1.fc36.noarch Reply at: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1972159/comments/61 ** Changed in: systemd (Fedora) Status: Unknown => Fix Released ** Changed in: systemd (Fedora) Importance: Unknown => Critical -- 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/1972159 Title: systemd-oomd frequently kills firefox and visual studio code Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Fix Released Status in systemd source package in Kinetic: Fix Released Status in systemd package in Fedora: Fix Released Bug description: [Impact] The "swap kill" side of systemd-oomd has caused unexpected behavior for desktop users. A user's browser, desktop session, or some other desktop application may be killed by systemd-oomd when SwapUsedLimit is reached, but system performance otherwise appears unaffected. This leaves users confused as to why their application was killed, and has a negative impact on their desktop experience. For now, let's disable the swap kill functionality by default. [Test Plan] On Jammy desktop, check the ManagedOOMSwap property on -.slice: $ systemctl show -- "-.slice" | grep "^ManagedOOMSwap" ManagedOOMSwap=kill # After the fix, this should print ManagedOOMSwap=auto [Where problems could occur] Disabling swap kill by default means that users may experience degraded system performance due to high swap usage, because systemd- oomd will no longer act on cgroups with high swap usage. [Other Info] If a user wishes to restore the original systemd-oomd behavior, they can do so by creating the following overrides file: $ cat /etc/systemd/system/-.slice.d/10-oomd-root-slice-defaults.conf [Slice] ManagedOOMSwap=kill [Original Description] Since I installed Ubuntu 22.04, firefox and visual studio code are frequently killed by systemd-oomd (every 2hours). I have 8 GB memory and never experienced this before the upgrade to Ubuntu 22.04. I thus assume that the claim that there is not enough memory is abusive. Did 64GB of memory become the minimum requirement to run Ubuntu ? The second problem is that it gives a very bad user experience which is critical for new Ubuntu users. There should be a warning prior killing apps to give the opportunity to save the app data. There should at least be an apologize and an explanation after killing the app. The current behavior gives the impression that Ubuntu 22.04 is unreliable and unsafe to use which is a problem for an LTS release that many people might want to use for critical production context. There might be a configuration problem with systemd-oomd or simply a bogus behavior. I would recommend to disable it or remove it completely until this problem is resolved. This is what I will do for myself because I have work to do. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1972159/+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
