Przejdź do treści

When Minecraft cannot allocate another object

A full heap prevents Java from allocating new objects. This identifies a specific memory shortage, but does not yet tell you whether your world needs more headroom or an extension keeps accumulating data.

An example of this log message

java.lang.OutOfMemoryError: Java heap space

Recognise the trigger in the timeline

Note whether the failure occurred while loading the world or after a longer session. Compare the memory trend with recent changes. A newly added chunk loader calls for a different investigation from an unchanged setup reaching its limits as more players join.

Run a manageable comparison

Back up the world. Temporarily reduce loaded chunks or revert the most recently added extension. Then repeat the same activity. If normal use still needs more headroom, check the RAM calculator and the resources available in your SupremeTier panel.

Questions about this error

Does this line prove a memory leak?

No. An ordinary workload peak can also exhaust the maximum heap. What matters is whether usage drops again after reducing the load.

Is a higher Xmx value enough?

The Java process needs memory outside the heap as well. Do not set Xmx above the resources actually available; check the existing startup configuration first.

Check memory requirements for your world

Check a connected log excerpt