Analyzing a heap dump is a fantastic suggestion for debugging this. Make sure you take the dump AFTER the memory leak has occurred, i.e. after a couple hours of uptime.
Additionally, you could use Java benchmarking software/suites to monitor your Java Heap growth in real-time, to see if there...
Hello sleepingnight,
The typical solution for this is to limit the # of water physics events that can process in a given tick, and to queue the remainder to occur over the next couple of ticks.
What version of spigot/bukkit are you using? Some of these have built in configurable options for...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.