Comment 47 for bug 1972159

(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 <email address hidden>.