Out of memory errors

The server crashed with OutOfMemoryError, Java heap space or GC overhead limit exceeded.

The server ran out of RAM: reduce what uses memory, find a leak, or upgrade the plan.

Before you start: The crash time and what changed recently (new plugin, mod, more players).

Step by step

1. Restart the server to get it running again.
2. Think about what changed: remove recently added plugins or mods one at a time to test.
3. Lower view-distance (8 is a good value) and simulation-distance (6) in Quick Settings.
4. Clear build-ups of entities and dropped items (see the entity guide).
5. If memory climbs slowly for hours and then crashes, it is a leak: add a daily restart in Schedules while you find the plugin with spark (spark heapsummary).
6. If the server is simply busy, upgrade the RAM from Billing; the world and plugins are kept.
7. Do not raise -Xmx in Startup above your plan: the server gets killed instead (exit code 137).

Check it worked: Statistics shows memory steady below about 85% at busy times, and no more crashes.

Why it happens: Too many players, loaded chunks, entities, plugins or mods for the plan, or a plugin/mod leaking memory.

If it runs out of memory with very few players right after starting, send support the crash report.

More guides on RAM, CPU, performance, and lag:

• Find out why your server lags
• RAM always shows high in the panel
• High CPU usage
• Too many entities, mob farms and item build-ups
• Redstone and hopper lag
• View distance and simulation distance