Closed T-h-o-r-p-e closed 1 month ago
Facing the exact same issue here on my Docker Server. Seems related to the Sakura update.
Before the update the server usually stayed around 6 GB RAM Usage, after the update it takes whatever is available until OS kills the process for memory reasons.
Grafana Memory overview of last night
18h is daily server restart. Around 19:30 did a manual restart for config changes. 02:45 is when the server crashed cause memory usage. and finally around 04:15 everyone stopped playing.
Checking my Grafana logs over a period of 7 Days indicates that issue started since 27/06 (Sakura Update day)
If anything I can provide to assist let me know.
Hi @MamboDead & @T-h-o-r-p-e,
Sadly I have no control over the memory usage of the application that is running in the container. I am afraid that this needs to be handled by the Palworld Devs.
Describe the bug
Server instability due to higher-than-expected ram usage (possible memory leak). After some hours of playing, the ram usage of the server grows higher and higher, until a point that the server crashes and restarts. At which point the ram returns to expected usage values. The issue does not seem to be related to the number of players, what is going on on the server, nor if users are online or not. It appears to simply occur as uptime increases. Restarting the server therefore restarts the 'countdown' to the next crash. (Restarting once a day is not enough)
To Reproduce
Steps to reproduce the behavior:
Expected behaviour
RAM usage stays relatively stable and does not climb uncapped to a point of a crash
Actual behavior
Total RAM usage by the server increases over time until it uses the max amount of RAM (and in my case Swap Memory) and then crashes the server.
Screenshots
OS information (IMPORTANT)
Hardware information (IMPORTANT)
docker-compose.yml contents (IMPORTANT)
Container/Host Logs (IMPORTANT)
Not sure where to locate this
Additional context
Bug Report Checklist