Why is modded KSP getting killed on Linux when I still have free RAM?

November 18, 2026 4 answers
Asked by scrimOnCaffeine

Kerbal Space Program gets through mod loading but crashes before the menu when running through Proton. KDE reports a low-memory kill, but only about 20 GB of 64 GB RAM appears to be in use, while nearly all 16 GB of swap is used. What should I check?

Answers

GBCportTuner

Start with the logs rather than assuming the whole machine ran out of RAM. A process can be killed because of a memory limit on its control group even when the system still has memory available. A userspace memory manager can also terminate a process under memory pressure.

Check the system journal around the crash for an out-of-memory message and which process or group was killed. If it points to a control group, inspect its memory.max, memory.current and memory.events files under /sys/fs/cgroup. That should help distinguish a local limit from system-wide exhaustion.

P6!HotbarCheck:

The KDE notification is a useful clue, but it doesn't by itself establish which limit was hit or which component made the decision.

Reply to this answer
stunFrameByFerry

Nearly full swap is worth investigating, but it doesn't automatically mean the kernel must kill something while plenty of usable RAM remains. Check MemAvailable in /proc/meminfo rather than relying only on a desktop usage graph. Also check for memory pressure and any limits on the game or its parent process.

More swap may give you room to test, but it won't fix a restrictive control group limit. The memory and swap numbers alone don't tell us the cause.

Reply to this answer
GBCresetRattle

For the mod side, try a clean launch with no mods, then add them back in batches. If the crash returns, narrow down that batch and check the game log for errors near the end. Keep a copy of the modded setup first so testing doesn't disturb your saves.

Reply to this answer
scrimBySunrise

I'd also test the native Linux version and a different Proton version as separate experiments. Keep the mod set the same when comparing them. That won't prove which mod is responsible, but it can show whether the failure depends on the runtime.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions