-
Notifications
You must be signed in to change notification settings - Fork 0
FAQ
If it doesn't continue to grow indefinitely, then it's normal.
Jvm Memory Model | Java Memory Beyond Heap | Is your Java application using more memory than the -xmx setting?
The maximum physical memory occupied by a Java process is:
Max Memory = eden + survivor + old + String Constant Pool + Code cache + compressed class space + Metaspace + Thread stack(*thread num) + Direct + Mapped + JVM + Native Memory
I won't give you any optimization parameters, because it doesn't work for everyone, you need to adjust it according to your Java distribution + CPU + memory + OS.
I generally don't recommend allocating more than 75% of the hardware's memory, especially if you're running the JVM on Windows or if there are other processes running in the same environment.
This can lead to frequent OOM (Out Of Memory) errors or other more serious consequences.
This error may be introduced by us (LevelBukkit) or upstream or patch provider. You can selectively perform simple tests in Vanilla, paper, folia, luminol and upstream in PATCH-LIST to check whether the problem can be reproduced. If the error is successfully reproduced in the corresponding upstream, you need to submit a report in the corresponding place.
LevelBukkit can't do anything about many bugs, such as those marked in the Issues roadmap, although we sometimes try to fix some.