Saltar para o conteúdo

Memory collection takes over the game

Java keeps trying to reclaim occupied heap but recovers too little space. Hardly any time remains for actual server work. A restart may temporarily clear this state without explaining why it developed.

An example of this log message

GC overhead limit exceeded

Look at the period before the warning

Were additional worlds loaded or demanding plugins enabled? Note whether delays grow during a session. This gives you something to compare with a shorter test under similar load.

Keep less data in memory at once

For the test, reduce loaded chunks and disable one suspect extension after taking a backup. Check whether the game responds again and the warning stops. If your intended workload still exhausts the heap, compare its RAM requirements with your selected offer.

Questions about this error

Is this identical to Java heap space?

Both involve memory pressure. Here Java fails because collection becomes too expensive; Java heap space identifies a failed allocation.

Should I turn off garbage collection?

That does not remove the cause. Start with workload and available heap rather than suppressing the protective warning through startup flags.

Check memory requirements for your world

Check a connected log excerpt