Minecraft Forums

I've tried editing the amount of memory used by minecraft, and I've reinstalled Minecraft and Java. Nothing seems to help. Only happens on this computer. Any help appreciated!! Here's the crash report:

---- Minecraft Crash Report -------- Minecraft Crash Report ----// There are four lights!
Time: 12/7/19 11:48 AMDescription: Initializing game
java.lang.OutOfMemoryError: Java heap space at java.util.Arrays.copyOf(Arrays.java:3332) at java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:137) at java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:121) at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:569) at java.lang.StringBuffer.append(StringBuffer.java:369) at java.io.BufferedReader.readLine(BufferedReader.java:370) at java.io.BufferedReader.readLine(BufferedReader.java:389) at org.apache.commons.io.IOUtils.readLines(IOUtils.java:1294) at org.apache.commons.io.IOUtils.readLines(IOUtils.java:1248) at org.apache.commons.io.IOUtils.readLines(IOUtils.java:1229) at cyg.a(SourceFile:238) at cyg.<init>(SourceFile:211) at cyc.au(SourceFile:440) at cyc.b(SourceFile:394) at net.minecraft.client.main.Main.main(SourceFile:155)

A detailed walkthrough of the error, its code path and all known details is as follows:---------------------------------------------------------------------------------------
-- Head --Thread: Client threadStacktrace: at java.util.Arrays.copyOf(Arrays.java:3332) at java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:137) at java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:121) at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:569) at java.lang.StringBuffer.append(StringBuffer.java:369) at java.io.BufferedReader.readLine(BufferedReader.java:370) at java.io.BufferedReader.readLine(BufferedReader.java:389) at org.apache.commons.io.IOUtils.readLines(IOUtils.java:1294) at org.apache.commons.io.IOUtils.readLines(IOUtils.java:1248) at org.apache.commons.io.IOUtils.readLines(IOUtils.java:1229) at cyg.a(SourceFile:238) at cyg.<init>(SourceFile:211) at cyc.au(SourceFile:440)
-- Initialization --Details:Stacktrace: at cyc.b(SourceFile:394) at net.minecraft.client.main.Main.main(SourceFile:155)
-- System Details --Details: Minecraft Version: 1.14.4 Minecraft Version ID: 1.14.4 Operating System: Windows 10 (amd64) version 10.0 Java Version: 1.8.0_51, Oracle Corporation Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation Memory: 1365871856 bytes (1302 MB) / 2147483648 bytes (2048 MB) up to 2147483648 bytes (2048 MB) CPUs: 8 JVM Flags: 9 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xss1M -Xmx2G -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=32M Launched Version: 1.14.4 LWJGL: 3.2.2 build 10 OpenGL: NO CONTEXT GL Caps: Using VBOs: Yes Is Modded: Probably not. Jar signature remains and client brand is untouched. Type: Client (map_client.txt) Resource Packs: ~~ERROR~~ NullPointerException: null Current Language: ~~ERROR~~ NullPointerException: null CPU: <unknown>

Ok I fixed it. I thought that installing and reinstalling Minecraft was sufficient, but I hadn't deleted the /.minecraft folder. When I did that and THEN reinstalled, the game launched.

Just a note for the event this happens again - you should never need to reinstall the game (I haven't in 6+ years) unless the launcher itself is corrupted since it verifies the integrity of all files every time you launch the game (in fact, modded versions need to force the launcher to not download unmodified files by removing lines that tell it where to download files from - otherwise, if you try to modify the game it will just redownload a clean copy, same for libraries and assets).

Usually, errors like this are either due to corrupted worlds, resource/data packs, or the options.txt file (these are all data files and are not verified by the launcher). options.txt, which stores game settings, is particularly notorious for causing all sort of issues, especially if you play on multiple versions (you should always run them in their own game directories), as indicated by the fact that it happened while the game was reading from a file ("java.io.BufferedReader.readLine").