You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 8, 2022. It is now read-only.
There seems to be a memory leak in a hashmap in ProfilerStatsMonitor. After an uptime of ~12 hours and ~10 active players, a hashmap in the class takes up a whooping 500MB of memory.
Skimming the code, it looks like we're populating a hashmap inside the stats attribute for each loaded chunk without clearing the hashmap. One way to fix this would be to listen on ChunkUnloadEvent and remove stale entries.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
There seems to be a memory leak in a hashmap in
ProfilerStatsMonitor
. After an uptime of ~12 hours and ~10 active players, a hashmap in the class takes up a whooping 500MB of memory.Skimming the code, it looks like we're populating a hashmap inside the
stats
attribute for each loaded chunk without clearing the hashmap. One way to fix this would be to listen on ChunkUnloadEvent and remove stale entries.The text was updated successfully, but these errors were encountered: