Direct answer

Recover safely from entity-heavy areas and identify the farm, mob, item, or modded entity source before restarting repeatedly.

What it means

An entity-heavy area can overwhelm tick time or memory, while a broken mod/plugin entity can also crash during ticking. The crash report/profiler is needed to distinguish raw quantity from faulty entity code.

If you are a player

  • Note the exact time the server froze, restarted, or disconnected you, plus what you were doing immediately beforehand.
  • Ask whether every player was affected at the same moment. A server-wide disconnect is much more useful evidence than one client having trouble.
  • Send the owner the disconnect text and, if available, your client log from that timestamp. Reinstalling the client is rarely useful for a server-wide crash.

If you run the server

  1. Stop repeated automatic restarts long enough to preserve the original log and crash report. Make a complete copy of the world and plugin/mod data before cleanup attempts.
  2. Read the crash report for Ticking entity, the entity type, position, dimension, and the first relevant mod/plugin stack frames. A bug in one entity class is not the same as too many legitimate entities.
  3. If the server stays online long enough, profile the affected area under normal load and identify whether entity AI, collisions, items, or XP orbs are consuming tick time. If the process crashes before a profile can run, use the saved report and test copy instead.
  4. In a restored test world, disable or redesign the farm/spawner/plugin creating excessive entities. If a specific broken entity prevents startup, use a version-compatible recovery tool on the copy only; verify what data would be removed before applying it.
  5. Restart the test server, visit the affected chunks, and check logs plus MSPT. Promote only the verified repair to production while keeping the untouched backup for rollback.

Important notes

  • More allocated RAM does not make a slow main-thread workload faster. Change heap size only when memory/GC evidence supports it.

References

Use the documentation for the exact software and release you run. These sources support the settings or diagnostic behavior used in this fix.

Was this article helpful?
Help us improve this article

Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.

What could we improve?
Do not include passwords, server IPs, or other private information.0 / 1000