> Please tell me which log (s) you require. journalctl -u systemd-oomd.service -b
would be a good start. If you rebooted since uninstalling systemd-oomd, please gather the logs from the most recent boot where the issue occurred. E.g., if it was the previous boot, you could use `-b -1` to specify that. Or, if it was two boots ago, you could do `-b -2`. See `man journalctl` for details. > Memory usage (before systemd-oomd removed) I don't have and I don't really want to reinstall systemd-oomd just to show the memory usage increasing Without this, there's not a clear way for me to investigate your issue. I (and many others) run systemd-oomd without this issue. > https://askubuntu.com/questions/1404888/how-do-i-disable-the-systemd- oom-process-killer-in-ubuntu-22-04 This does not say anything about systemd-oomd *causing* increased memory usage. This is about systemd-oomd *killing* processes with high memory usage, as it is designed to do. We had issues with it being too aggressive in the past, which is what that and other reports are about. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2097016 Title: systemd-oomd package causes iconstant increase in memory usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2097016/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
