What the OOM Killer Does, and Why Your Process Got Killed

Your app or game server suddenly died with no crash log, no error message, nothing — just gone. Check dmesg or your system log and there's a good chance you'll find the real culprit: the Linux OOM killer.

What It Actually Is

OOM stands for "out of memory." When a Linux system (including your VPS or container) runs completely out of available RAM, the kernel has to do something rather than let the whole system lock up — so it picks a process (using a scoring system that weighs memory usage against a few other factors) and kills it outright, immediately, no warning to the app itself.

This is a kernel-level safety mechanism, not a bug in your software or in our infrastructure — it exists on every Linux system, including ones you'd run yourself on bare metal.

How to Tell If It's What Happened

dmesg | grep -i "killed process"

or check /var/log/syslog / /var/log/kern.log for a line mentioning Out of memory and Killed process. If you see your process named there, that's your answer — it wasn't a crash in the traditional sense, it was killed from outside.

Why It Happens

• Your app/server is using more RAM than your plan actually has, especially under load spikes.
• A memory leak in a long-running process (common with poorly-optimized plugins/mods) slowly eats available RAM until nothing's left.
• Too many processes running simultaneously on a small plan (a game server plus a web panel plus a monitoring agent, all fighting for the same limited RAM).

What To Do About It

1. Check actual usage with free -h or htop to see how close you are to your limit under normal load.
2. Find the leak if it's a specific process growing over time rather than a one-time spike — restarting on a schedule is a workaround, not a fix, but it buys time while you find the actual cause.
3. Reduce concurrent load — fewer plugins, lighter startup flags, or moving a second service to its own VPS instead of sharing.
4. Upgrade RAM if you're consistently near the ceiling under normal (not just peak) usage — see our VPS add-ons for adding RAM without a full tier jump, or the VPS plans comparison if you need a bigger overall jump.

On Game Panel Servers Specifically

Pterodactyl-style game servers usually set a hard memory limit that stops the process cleanly with its own message rather than letting the kernel OOM-kill it — if you're seeing a silent OOM kill specifically, it's more often on VPS plans where you're managing memory yourself, not on our game hosting products.

A silent, logless death is almost always memory-related on Linux — checking dmesg first saves a lot of guessing.