Palworld live issue tracker
Palworld dedicated server RAM grows until it crashes
Track dedicated-server memory that climbs over hours and is not fully released, ending in a crash at peak player counts. Community server hosts describe the pattern consistently; Pocketpair lists server-side optimization in 1.0 but has not confirmed a specific leak.
The graph will appear when players respond.
Updated 08:33 UTC. Refreshes every 60 seconds.
Affected hardware patterns
No hardware pattern clears the privacy threshold yet. Small groups stay hidden.
What is known, and what is not
The graph counts anonymous responses
It shows report volume and comparison responses. It does not diagnose the cause or prove every report has the same cause.
Not acknowledged
Pocketpair has not acknowledged this specific tracker in the checked official sources.
Supported workaround available
Schedule a periodic server restart (community hosts commonly use every 4 to 12 hours) and size RAM with headroom above the expected player count instead of at the minimum.
Workaround sourceAffected scope
Evidence sources
- Official: No publisher acknowledgement source is attached.