
Memory leak when using WG with MythicDungeons
Closed this issue · 2 comments
WorldEdit Version
7.3.16+cbf4bd5
WorldGuard Version
7.0.14
Platform Version
Leaf-1.21.8
Confirmations
- I am using the most recent Minecraft release.
- I am using a version of WorldEdit compatible with my Minecraft version.
- I am using a version of WorldGuard compatible with my Minecraft version.
- I am using the latest or recommended version of my platform software.
- I am NOT using a hybrid server, e.g. a server that combines Bukkit and Forge. Examples include Arclight, Mohist, and Cardboard.
- I am NOT using a fork of WorldEdit, such as FastAsyncWorldEdit (FAWE) or AsyncWorldEdit (AWE)
Bug Description
When WG is installed at the same time as MythicDungeons, the memory used by MythicDungeons will not be released when the dungeon loop is completed multiple times.
After about 180 copy cycles, the server memory will be full of 32G, and then the memory will overflow, making it impossible to play on the server normally.
Expected Behavior
Releases the MythicDungeons world from memory after the instance is completed.
Reproduction Steps
- 安装WG和MythicDungeons
- 多次完成副本
- 持续观察内存占用
Optional WorldGuard-Report
No response
Anything Else?






You should report this issue to the MythicDungeons developers, as the plugin’s Spigot reviews show that it alone is causing memory leaks for many users and is unrelated to WorldGuard.