Server version
1.21.10
Duels version
7.2
Heap dump
We attempted to analyze the heap dump internally to identify the exact cause, but unfortunately, the size of the file generated during the Duels sessions is so massive that it is impossible to open or analyze it on our local PCs.
If you are willing to take a look at the file yourself, please let me know here or contact me privately; I will make sure to upload it to an external cloud storage and provide you with the download link.
Uncleared object(s)
No response
Additional info
During our extensive testing and resource monitoring, we also encountered a severe Memory Leak issue caused by the plugin.
Under normal conditions, our server maintains a stable average consumption of around 2 GB of RAM. However, as soon as duels are started (even with very few active players), the RAM usage rapidly spikes up to 6-8 GB.
Although our current infrastructure can handle this load, we prefer to keep resource consumption optimized to a minimum. Furthermore, this level of memory usage would make the plugin completely unusable for smaller servers. For this reason, we have decided to temporarily disable the Duels feature until this issue is resolved.
Unfortunately, we haven't been able to isolate more specific data (such as heap dumps or precise stacktraces) within the plugin to pinpoint the exact source of the leak, but we are 100% certain that the RAM spike is triggered by the duel sessions. We hope this information helps you investigate the codebase.
Checklist
Server version
1.21.10
Duels version
7.2
Heap dump
We attempted to analyze the heap dump internally to identify the exact cause, but unfortunately, the size of the file generated during the Duels sessions is so massive that it is impossible to open or analyze it on our local PCs.
If you are willing to take a look at the file yourself, please let me know here or contact me privately; I will make sure to upload it to an external cloud storage and provide you with the download link.
Uncleared object(s)
No response
Additional info
During our extensive testing and resource monitoring, we also encountered a severe Memory Leak issue caused by the plugin.
Under normal conditions, our server maintains a stable average consumption of around 2 GB of RAM. However, as soon as duels are started (even with very few active players), the RAM usage rapidly spikes up to 6-8 GB.
Although our current infrastructure can handle this load, we prefer to keep resource consumption optimized to a minimum. Furthermore, this level of memory usage would make the plugin completely unusable for smaller servers. For this reason, we have decided to temporarily disable the Duels feature until this issue is resolved.
Unfortunately, we haven't been able to isolate more specific data (such as heap dumps or precise stacktraces) within the plugin to pinpoint the exact source of the leak, but we are 100% certain that the RAM spike is triggered by the duel sessions. We hope this information helps you investigate the codebase.
Checklist