Bug Closed · Resolved

The server memory only increases without decreasing

#5229 opened by Unknown 2 years ago

Unknownreported this bug

In some specific situations, such as default teaming up? It will cause the server memory to continue increasing until the memory overflows and the server crashes I can only find that mythicdungeons has this class from these two Java classes

plz check on java.until.concurrent.ConcurrentLinkedQueue

I can only find that mythicdungeons has this class from these two Java classes

# Whether only the party leader is allowed to start a dungeon for the party. LeaderOnlyQueue: true

# Whether to require all party members confirm they're ready before entering a dungeon after waiting in the queue. ReadyCheckInQueue: true

[Legacy attachment omitted]

Unknowncommented

How long is your server up for before things crash? What are the specifications? How many players/dungeons are you roughly getting before it crashes?

Unknowncommented

It ran for about 6 hours before crashing, with a running memory of 32GB After about 8-12 players enter the dungeon, this type of game begins to appear I have tested removing MythicDungeons Plugin for 1 day without encountering any memory overflow issues of this class Adding MythicDungeons causes this issue

Unknowncommented

So this is after the dungeon gets instanced 8-12 times, or is this after they repeatedly enter your dungeons?

There is an inherent memory leak with Minecraft world management like this in general that requires restarts, which is why we're working on a proxy system so you can have dungeon servers to mitigate this issue. But it should not be reaching the numbers you're showing me unless people are actively running dungeons repeatedly on your server during those 6 hours.

Are your instances properly closing, as in are their folders being deleted or are they staying open?

Unknowncommented

Instance closed and deleted normally The inherent memory still exists

Players have not been able to enter and exit the dungeon without any restrictions. I have set permission cooldowns for them

Unknowncommented

Are you using ModelEngine mobs and what version of MythicMobs are you using?

Unknowncommented

To make this issue not useless without OPs answer, I ran into the same issue, did a full heapdump (32 GB file size) and can confirm that it's caused by latest non-development version of ModelEngine with MythicDungeons. I had the exact same results with ConcurrentLinkedQueue and it contained ModelEngine references. This ONLY happens if ModelEngine is installed, the problem is not persisting when is only one of them present. [Legacy attachment omitted] [Legacy attachment omitted]

Unknowncommented

Can you please check with the latest development build of Model Engine? This should have been fixed and verification from a third party would be greatly appreciated! This is also in general with using ModelEngine, not even this specific use-case of OP.

Unknowncommented

Will do! I'll check it after 20 hours if the issue persists since it takes some time.

Unknowncommented

Development version of ModelEngine fixes the issue. I just did a HeapSummary from Spark and it seems the Memory Leak is not there. The server RAM is also hovering at the same usage as it did before adding MythicDungeons back. [Legacy attachment omitted]

Sign in to join the discussion.