The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →-Xmx3G is a request, not a guarantee. It sets the maximum Java heap for a Minecraft server, while the Java process also needs native memory and the computer must reserve room for the operating system and other programs. A 3 GB server can fail to start, be killed by a hosting panel, or appear to use more than 3 GB when Java, the host, and the hardware impose different limits.
Godlike.Host offers hosted Minecraft Java servers with its own game panel, SFTP access and free DDoS protection, if you would rather not host it yourself.
The reliable fix is to identify which ceiling you have hit: a 32-bit Java process, a panel or container limit, insufficient physical or virtual memory, or a startup command that configures the client instead of the dedicated server.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Minecraft | Java & Bedrock Deluxe Collection | Windows Digital Code | $39.99 | Buy on Amazon |
| 2 |
|
Minecraft | Java & Bedrock Ultimate Collection | Windows Digital Code | $49.99 | Buy on Amazon |
| 3 |
|
Minecraft | Standard Edition | XBOX Digital Code | $19.99 | Buy on Amazon |
| 4 |
|
Minecraft | $6.99 | Buy on Amazon |
| 5 |
|
Minecraft - Bedrock Edition PS4 | $42.98 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
Recommended Free Tools
What -Xms3G and -Xmx3G actually do
Java divides memory into several areas. The heap stores most Minecraft world objects and is the area controlled by the familiar flags:
-Xmssets the heap size Java starts with.-Xmxsets the largest heap Java is allowed to grow to.
A fixed-size server command commonly looks like this:
#1 Best Overall
- DELUXE COLLECTION — Includes Minecraft: Java & Bedrock Edition, three Bedrock add-ons, three exclusive Character Creator items, and 700 Minecoins.
- CREATE YOUR WORLD — Build whatever you imagine in an infinite world that’s unique in every playthrough.
- EXPLORE AND CRAFT — Discover biomes, resources, and mobs, then craft your way through a sandbox world filled with surprises.
- SURVIVE THE ADVENTURE — Face mysterious foes, travel across exciting landscapes, and venture into perilous dimensions.
- PLAY TOGETHER — Play cross-platform with friends in Bedrock Edition on console, mobile, and PC, or join community servers in Java Edition on PC, Mac, and Linux. Online console multiplayer requires a platform-specific subscription (sold separately).
java -Xms3G -Xmx3G -jar paper.jar --noguiUsing the same value for both flags asks Java to start with a 3 GiB heap and permit a maximum of 3 GiB. It does not cap the entire process at 3 GiB. Java also needs memory for the virtual machine, thread stacks, class metadata, JIT-compiled code, garbage-collection structures, direct buffers, native libraries and mapped files. Paper’s documentation therefore warns that the process can use a little more than -Xmx. A host limit set to exactly 3 GB can kill a server configured with -Xmx3G even when the heap itself has not exceeded 3 GB.
The suffix is a unit understood by the JVM. 3G is a binary-style gigabyte value used for JVM sizing; it is not a promise that an operating-system task manager will display exactly 3.00 GB. Display tools may report GiB, decimal GB, committed memory or resident memory, so their numbers will not match perfectly.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteThe four memory ceilings that can block a 3 GB heap
| Ceiling | What it limits | Typical symptom | Where to change it |
|---|---|---|---|
| Java process architecture | The address space available to one JVM, especially with 32-bit Java | Startup says it cannot reserve the object heap, or a large heap is rejected immediately | Install a compatible 64-bit Java runtime and point the server script to it |
| Virtual and physical memory | Memory the operating system can commit and keep available | Heap reservation fails, swapping becomes severe, or the operating system terminates the process | Lower the heap, close other programs, add compatible RAM, or increase available virtual memory where appropriate |
| Panel or container quota | The maximum memory assigned by a control panel, container, VM or managed host | Server is killed without a normal Java crash, often near the quota | Leave headroom, lower -Xmx, or have the host raise the quota |
| Wrong launch target | The command or launcher you edited, rather than the dedicated server process | Changing launcher arguments has no effect on Paper, Spigot, Fabric, Forge or vanilla server startup | Edit the server’s batch file, shell script or panel startup field |
These ceilings stack. A 64-bit JVM can still fail inside a container with a 2 GB limit, and a panel with plenty of quota cannot overcome a computer that has no free memory.
First confirm that you are configuring the dedicated server
The Minecraft Launcher’s installation settings control a client instance. A separately launched Paper, Spigot, Fabric, Forge or vanilla server reads the command, script or panel field used to start that server. Changing client JVM arguments will not automatically change a dedicated server.
Find the server startup command
Look for a Windows .bat file, a Linux or macOS shell script, a panel’s “Startup” or “Launch” field, or the command you type in a terminal. The server-side syntax has the Java flags before -jar:
java -Xms3G -Xmx3G -jar paper.jar --noguiFor another server implementation, keep the flags in the same position and replace the jar name with the file that implementation supplies. Some modded distributions add their own argument files or scripts; follow that script’s documented launch path instead of adding a second, conflicting command.
Rank #2
- ULTIMATE COLLECTION — Includes Minecraft: Java & Bedrock Edition, five Bedrock add-ons, five exclusive Character Creator items, and 1000 Minecoins.
- CREATE YOUR WORLD — Build whatever you imagine in an infinite world that’s unique in every playthrough.
- EXPLORE AND CRAFT — Discover biomes, resources, and mobs, then craft your way through a sandbox world filled with surprises.
- SURVIVE THE ADVENTURE — Face mysterious foes, travel across exciting landscapes, and venture into perilous dimensions.
- PLAY TOGETHER — Play cross-platform with friends in Bedrock Edition on console, mobile, and PC, or join community servers in Java Edition on PC, Mac, and Linux. Online console multiplayer requires a platform-specific subscription (sold separately).
Check which Java executable is used
A panel or script may call a different Java installation from the one available when you open a terminal. On Windows, put the following in the server directory or run it in the same environment as the server:
where java
java -versionOn Linux or macOS, use:
which java
java -versionThe version output should identify a 64-bit VM. If the path points to an old 32-bit installation, changing only -Xmx will not solve the address-space limit. Install a 64-bit Java version compatible with your Minecraft server release, then update the script or panel to invoke that executable explicitly. Re-run the version command from that exact startup context before testing the server.
Why 32-bit Java rejects large allocations
A 32-bit process has a much smaller address space than a 64-bit process. The Minecraft Help guidance states that 32-bit operating systems have a 4 GB RAM maximum. That figure describes the platform’s broad ceiling, not a guarantee that a Minecraft JVM can reserve a 3 GB heap: the operating system, executable, libraries and JVM itself consume part of the address space, and allocations can fail before the nominal maximum.
Oracle’s Java guidance identifies the process data model—32-bit or 64-bit—as one of the limits on heap size. A practical fix is:
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problems- Run
java -versionusing the executable that actually launches the server. - Verify that the output reports a 64-bit VM.
- Install a 64-bit runtime if it does not.
- Change the server script or panel command so it uses that runtime’s full path, if more than one Java installation exists.
- Start with a conservative heap, then increase it only after the server starts reliably.
Do not assume that a 64-bit operating system automatically means the server is using 64-bit Java. The executable selected by PATH, a panel image or a bundled runtime determines the process architecture.
Check the panel, container or virtual-machine limit
Managed hosts and self-hosted containers often enforce a hard memory quota. The quota applies to the whole process, not just the Java heap. Because a server configured with -Xmx3G can use more than 3 GB in total, a 3 GB container limit leaves no room for native JVM memory and can trigger an out-of-memory kill.
Rank #3
- CREATE YOUR WORLD — Build whatever you imagine in an infinite world that is unique in every playthrough.
- EXPLORE AND CRAFT — Discover biomes, resources, and mobs, then craft your way through a sandbox world full of surprises.
- SURVIVAL ADVENTURES — Face mysterious foes, travel across varied landscapes, and venture into perilous dimensions.
- PLAY TOGETHER — Play solo or join friends in local split-screen and cross-platform play across console, mobile, and PC. Online multiplayer supports up to 8 players.
- COMMUNITY PLAY — Connect with players on community servers, or subscribe to Realms Plus (sold separately) to play with up to 10 friends on a private server.
How to recognize a host-level kill
- The server disappears or restarts without a normal Java crash report.
- The panel reports “out of memory,” “OOM,” or a container limit violation.
- The Java log stops abruptly while the panel’s memory graph is at its cap.
- The same command works on an unrestricted machine but fails in the hosted environment.
On Linux systems where you have permission to inspect the kernel log, Paper recommends:
dmesg -T | grep -i killedA matching entry can show that the operating system’s out-of-memory manager, rather than Java’s exception handler, terminated the process. Containers may record the event in their own runtime or service logs instead.
Free tools Windows power users keep installed
One-click scans. No signup required.
Leave quota headroom
Lower -Xmx until the complete process fits below the quota, rather than setting the heap equal to the quota. If the server needs a larger heap, increase the panel or container limit. On managed hosting, only the provider can make that change. If you control the container, raise its memory setting and verify that the physical machine can supply the new limit.
Paper’s troubleshooting guidance suggests reducing -Xmx by roughly 1–2 GB as an initial diagnostic move when a panel kills the process. That is a test, not a universal final allocation: the correct value depends on the server’s workload and the amount of non-heap memory it uses.
Check total physical RAM before increasing the heap
A server cannot safely claim all installed memory. Oracle states that a single Java application’s heap should never be set to the machine’s entire physical RAM because the operating system, other processes and additional JVM operations need memory. Minecraft Help gives a general recommendation of no more than half of physical RAM for a single Java allocation on 64-bit systems.
That recommendation is a ceiling for planning, not an instruction to assign exactly half. A computer running a desktop, backup service, web server, voice chat or other game servers needs more headroom than a machine running only Minecraft. If the machine has 8 GB installed, a 3 GB heap may be reasonable in one setup and too large in another; measure what else is running instead of relying on the installed total alone.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Rank #4
- Skins! We have biome settlers, city folk, town folk, and more!
- The Nether and all its inhabitants. Fight Ghasts and make friends with Pigmen
- Cross platform play for up to five players between Pocket Edition and Windows 10
- Revamped touch controls, controller support, and a controller mapping screen
- Enhanced Weather effects! Accumulating snow and more
Use a conservative allocation test
- Close applications that are not required for the server.
- Start with a lower pair such as
-Xms2G -Xmx2G. - Confirm that the server reaches the “Done” state and remains stable while players join.
- Increase both values in small steps only if monitoring shows a genuine heap shortage and the host still has headroom.
If the computer is routinely short of memory, lower the heap, move other services elsewhere or install additional compatible RAM. A physical upgrade requires checking the motherboard or computer’s supported memory type, capacity, speed and module configuration; “16GB DDR4 RAM kit” is not a universal fit.
Choose sensible -Xms and -Xmx values
Matching values, for example -Xms3G -Xmx3G, create a fixed-size heap that avoids repeated heap expansion. They do not bypass any ceiling and do not reserve only 3 GB for the entire process. Both values must fit within the machine and host limits.
If startup fails, lower both flags and retest. Keeping -Xms high while lowering only -Xmx can still make Java reserve more memory than the machine or container can provide at startup. Conversely, an unnecessarily large initial heap can make a lightly used server consume memory that other services need.
Paper’s documented form
Paper documents this general launch structure:
java -Xms4G -Xmx4G -jar paper.jar --noguiThe 4 GB values are an example of syntax, not a recommendation for every computer. Replace them only after checking Java architecture, available memory and any panel quota. For a 3 GB target, the equivalent form is:
java -Xms3G -Xmx3G -jar paper.jar --noguiUse the same logic for other server types, while respecting each project’s current startup instructions and argument files.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Read the exact failure instead of guessing
“Could not reserve enough space for object heap”
This message means the JVM could not reserve the requested heap. The likely categories are a 32-bit process, insufficient virtual or physical memory, fragmented or restricted address space, or a host limit. Verify the Java architecture first, then check free memory and the panel quota. Lower -Xms and -Xmx together to establish a known-good baseline.
Best Value
- Play and share with friends on console, mobile and Windows 10
- discover community creations in the new in-game store
- access new mini games and game modes through servers
Process killed with no Java crash log
An abrupt exit points toward the operating system, container or control panel. Inspect the panel event log and, on Linux where available, search the kernel log with dmesg -T | grep -i killed. Reduce the heap to leave quota headroom or raise the external limit. Java cannot catch a termination performed by the host’s out-of-memory manager.
Java appears to use more than 3 GB
That can be normal. The heap limit applies to the Java heap, while the process includes native memory and other JVM areas. A high memory reading alone is not proof of a leak. Paper advises treating it as a problem when it is accompanied by out-of-memory crashes, failed allocations or unhealthy garbage-collection times—not merely because the operating system reports usage above -Xmx.
The server starts, but memory keeps rising
Java may retain committed heap for faster future allocations and garbage-collection efficiency. Watch for actual symptoms: crashes, allocation errors, long pauses or a host-level kill. If those occur, inspect plugins, mods, world activity and the available headroom after the basic architecture and quota checks. Do not raise -Xmx simply because the process has not returned every unused page to the operating system.
A complete diagnostic order
Use this order so each test isolates one class of limit:
- Identify the process. Confirm that you are editing the dedicated server command, not the Minecraft Launcher’s client JVM arguments.
- Record the exact command. Note the values of
-Xms,-Xmx, the jar or argument file, and any panel startup variables. - Verify Java architecture. Run
java -versionthrough the same path and environment used by the server; confirm 64-bit Java. - Check external quotas. Read the panel, container or virtual-machine memory limit and compare it with the complete process requirement, not just the heap value.
- Check the machine. Look at available physical memory while the server starts and account for the operating system and every other service.
- Lower both heap flags. Test a smaller pair, such as
-Xms2G -Xmx2G, then increase gradually only when the baseline is stable. - Classify the failure. Use Java logs for reservation errors and system or panel logs for abrupt OOM kills.
- Change hardware only when necessary. If the workload genuinely needs more memory and the platform supports it, add compatible RAM or move the server to a machine with more capacity.
Do not confuse client defaults with dedicated-server settings
Minecraft Java Edition 26.1 increased the default client allocation to 4 GB from 2 GB. That change affects how the official client launcher may configure a game installation. It does not automatically assign 4 GB to a separately launched Paper, Spigot, Fabric, Forge or vanilla server. Dedicated servers still use their own command, script, panel setting or argument file.
Conversely, changing a server script does not increase the client’s allocation. Diagnose the process that is failing before changing any memory field.
When each fix is appropriate
| Fix | Limit addressed | Reversible? | Trade-off |
|---|---|---|---|
| Install and invoke 64-bit Java | 32-bit process address space | Yes | Requires a runtime compatible with the server version and a corrected path |
Lower -Xms/-Xmx |
Physical, virtual or panel limits | Yes | Less heap headroom for large worlds, player counts or mods |
| Raise a panel or container quota | Host-imposed ceiling | Usually | May require a larger hosting plan or a machine with sufficient RAM |
| Close other services | Available physical memory | Yes | Those services will no longer run concurrently |
| Install compatible RAM | Physical-memory capacity | No, without removing the hardware | Requires motherboard checks, purchase and installation |
| Move to a larger machine | Physical and host capacity | Reversible as a migration decision | Involves migration work and potentially recurring hosting costs |
Practical launch examples
Windows batch file
@echo off
java -Xms3G -Xmx3G -jar paper.jar --nogui
pauseSave the command in the server directory and ensure the java found by that environment is the intended 64-bit runtime. The pause line keeps a failed console open so you can read the error; it does not change memory allocation.
Linux shell script
#!/usr/bin/env bash
exec java -Xms3G -Xmx3G -jar paper.jar --noguiRun the script from the directory containing the jar, or use an absolute path to both Java and the jar when multiple installations or services are present. If a service manager starts the script, inspect that service’s environment rather than assuming it inherits your interactive shell’s PATH.
What a successful fix looks like
- The server starts with the intended 64-bit Java executable.
- The panel or container’s limit is higher than the complete process requirement, not merely equal to
-Xmx. - The machine retains memory for the operating system and other required services.
- The server reaches its ready state without reservation errors or host-level OOM events.
- Memory observations are interpreted with Java’s non-heap usage and retained heap in mind.
Once those conditions hold, adjust the heap for the workload rather than chasing a particular number in a monitoring tool. A stable 2 GB heap is better than a repeatedly killed 3 GB configuration, and a correctly sized 3 GB heap is useful only when the Java process, host quota and physical machine can all support it.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
