#4759 opened by Unknown 2 years ago
version of MD : 1.2.2
Each time player create an instance dungeon map, minimum memory gradually rises after GC
so the restart cycle is very short due to this issues.
[Legacy attachment omitted] [Legacy attachment omitted]
memory graph when 10 map created:
[Legacy attachment omitted]
memory graph when 100 map created:
[Legacy attachment omitted]
Hey there.
Thanks for the super thorough statistics and info, this is actually a huge help.
I will, however, let you know that this is a very difficult issue to resolve and has to do with Bukkit/Spigot (and its forks) behind-the-scenes, and we have very little power over it. We have done as much as we can, and will continue to look into ways of improving this, but beware that it may take a while for any significant progress! At the very least, builds of 1.3.0+ should still improve this at least a little bit.
Having said that, I'm going to make this the primary issue on the tracker for discussion around this issue.
Have you observed any dungeon maps getting stuck, as in not unloading at all? You can tell by checking your main server folder for dungeon world folders ([dungeonname]_[number]) and comparing it with the /md status command.
i checked both, same count. But often there were when it didn't same.
Hey there! I've been doing a deep dive into the memory leak issues recently to see if there's anything we can do about it and I've got a couple questions.
Next, would you be willing to try one of your dungeons on a clean server, without any extra plugins aside from Mythic Dungeons and ProtocolLib? You can delete the functions.yml file from the copied dungeon to make sure it loads. Load the exit the dungeon repeatedly and see if it still creates a memory leak.
Hey there! This should, in theory, be fixed in the latest dev builds. Please give that a try and let me know if the issue continues.