Fix Palworld Server Crashes

Palworld is a great game, but it’s still new and has some problems, like servers running out of memory fast. This happens because of a memory leak in the game. In this article, you will learn about the common sources of memory leaks and how to fix them!

---

Common Crash: Out of Memory

An OOM (Out of Memory) crash happens when the game server demands more RAM than what is available from:

• The host node where your game server is located doesn't have any more physical RAM.

• For Providers like OASIS.HOST, your Server wants to use more RAM than allocated.

Why is the RAM usage so high?

Palworld’s dedicated server has had a serious memory leak since the first week of launch. The RAM usage can jump from 2GB to 8GB in a few hours of playing.

This is not normal and should not happen. This is a flaw/bug that Pocketpair will probably fix soon. The bug prevents the server from freeing the RAM it doesn’t need anymore because it doesn’t know what to free. We don’t know the exact cause of the memory increase, but it could be anything from Pals not being removed, to resource wasting bugs, to any other aspect of the dedicated server.

The good news is that you can do some things to lower the memory effect and make this memory leak bug less harmful.

Hotfix to reduce Memory Leak

We recommend disabling the bEnableInvaderEnemy setting, this can dramatically reduce RAM usage and the impact the memory leak has.

Despite what you might think, disabling this option doesn't disable Base Raids, so it's unclear what this specifically changes.

Changing the Setting

Navigate to /Pal/Saved/Config/LinuxServer/PalWorldSettings.ini and edit it either using our Panel's File Manager or SFTP Client and change bEnableInvaderEnemy=True to bEnableInvaderEnemy=False

OASIS.HOST Filemanager

Automatic restarts

Automatic restarts are still recommended, due to the memory leak - Changing the setting above does not fix the Issue.

Depending on your Server's player count and server package the recommended restart cycles can vary. We recommend the following for our Medium Palworld package:

• 4-8 Users, every 8 Hours.

• 8-16 Users, every 12 Hours.

Setup the Schedule in our Panel

• Navigate to Configuration > Schedules

• Click on Create Schedule to create a new schedule

• Set Minute to 0

• Set Hour to */[HOUR]

• To set the server restart interval, replace {HOUR} with the number of hours. For example, to restart every 12 hours, use */12

• Press Create Schedule

• Click on Manage Schedule and create a new Task

• Set Action to Send power action

• Set Time Offset to 0

• Set Payload to Restart the server

• Press Create Task