An unexpected issue occurred and the game has crashed
Crashes while trying to play 1.13.1 Same issue whether using file from 12.x or creating a new world. No error code, attaching the game output. All drivers are up to date. Using AMD video card. No mods.
Environment
Windows 10
Linked Issues
duplicates1
Created Issue:
An unexpected issue occurred and the game has crashed
Crashes while trying to play 1.13.1 Same issue whether using file from 12.x or creating a new world. No error code, attaching the game output. All drivers are up to date. Using AMD video card. No mods.
Environment
Windows 10
Added Affects Versions: 1.13.1
Removed Affects Versions: 1.13.2-pre1
Added Linked Issues:
duplicates
Added Attachments:
Added Attachments:
Added Linked Issues:
duplicates
Removed Linked Issues:
duplicates
Please do not mark unreleased versions as affected.
You don't have access to them yet.
Is this
MC-12949?-Xms256M is not enough to run Minecraft. See
MC-12949to increase memory.Proposed change to increase memory was unsuccessful. Still getting the same issue. Increased the memory to both 4G and 6G, still crashes in version 1.13 and higher.
Please attach the crash report found in .minecraft/crash-reports.
crash report attached
Probably has something to do with that. Try using Xmx1G -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=16M.
Edit: You have 2 -Xmx flags -Xmx6G and -Xmx256M...
Still crashing, no crash report being created. Here is the game output. Used the same name as before: error.txt
Can you post your JVM arguments?
-Xmx1G -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=16M
I don't see the second Xmx flag -Xmx256M
I thought that was your problem, but apparently not. Also, you seem to be having the same issue as
MC-135697.Does
MC-74465fix your issue?That fixed the issue! Make sure people know to use command prompt as Admin, and just have them copy/paste that command into the prompt. Then find the java setting that is forcing to 256M and delete that line. Good detective work. Thanks!