Hey everyone! I've been having a really frustrating issue with my laptop where it just freezes and reboots unexpectedly. It seems to happen a lot after I open Steam and a few other apps. After checking the logs, I suspect it's related to the Out-Of-Memory (OOM) killer. Here's what I found in the logs:
```
Sep 19 21:16:08 my-laptop systemd[1]: Starting systemd-oomd.service - Userspace Out-Of-Memory (OOM) Killer...
...
Sep 19 21:16:08 my-laptop systemd-oomd[1228]: Killed: No
```
My setup is:
* CPU: 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz
* GPU: Intel® Iris® Xe Graphics
* RAM: 7.5 GiB usable
* Storage: 1 TB HDD (considering adding an SSD)
* OS: Ubuntu LTS 24.04, GNOME 3.36.8
So, do you think the OOM killer is the culprit? If so, what steps can I take to prevent my laptop from freezing in the future?
3 Answers
From your logs, it looks like systemd-oomd didn’t actually kill any processes, so it may not be the direct cause of your freezing issues. Instead, the OOM killer is triggered when your system is low on memory. You're running Ubuntu 24.04, which uses newer GNOME, so make sure you're checking the correct logs. You can see what processes have been killed with this command: `dmesg -T | egrep -i 'killed process'`. Also, if you don’t really need the OOM killer for a desktop setup, you could disable it by running `sudo systemctl disable --now systemd-oomd`.
It sounds like your system is running out of resources when you try to open Steam and other apps. You might want to increase your swap space to give your system more breathing room. Even though 8GB of RAM is decent for everyday tasks, gaming can be quite demanding. Consider adding more RAM if you're planning to game frequently! You can keep an eye on memory usage by running this command in the terminal: `watch free -m`. That'll help you monitor how much memory you're using in real time.
While tools like GPT can offer some basic insights, they might not always hit the mark. To really understand what's going on, you need to examine your OOM logs closely. The systemd logs you shared aren't everything you need. Make sure to check if your OOM killer is working correctly and analyze the output more thoroughly to identify what’s actually causing the freezes.

Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures