Skip to main content

Rust exits after an update. Was it short of memory?

Check what happened to memory at the time of the exit. An update can make a memory problem visible, but the dates alone do not establish why the game stopped.

Find the exit and the limit

On Linux, look for a kernel out-of-memory entry naming the game. If a container or service has its own memory allowance, check its memory events too. Host memory can look comfortable while a single service has reached its cap. Compare the time with the latest game startup and with an earlier healthy run of the same map.

Change what the evidence points to

If memory really ran out, remove a competing workload or increase capacity for this server before attempting another start. If the first failure instead names a missing file or gives a game error, investigate that. After correcting the cause, check that Rust finishes loading the same world and remains stable through a normal busy session.

Sources

Analytics settings

Analytics are off.

Help improve RustSC with page counts and performance measurements. Privacy details