Minecraft Forums

Hola a todos.

Desde hace unos días mi hjo no puede jugar su Minecraft, debido a que da un fallo en el protocolo Java:

---- Minecraft Crash Report -------- Minecraft Crash Report ----// This doesn't make any sense!
Time: 27/10/19 11:59 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 7 (amd64) version 6.1 Java Version: 1.8.0_51, Oracle Corporation Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation Memory: 1446071072 bytes (1379 MB) / 2147483648 bytes (2048 MB) up to 2147483648 bytes (2048 MB) CPUs: 4 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>

Necesitamos de su ayuda para restaurar la jugabilidad del mismo.

Saludos

Reinstall Minecraft from scratch.

Try allocating more memory to Minecraft, try -Xmx4G in the JVM arguments.

Gracias Conor, realice los paso que dijistes y aumente la memoria RAM a 3G pero sigue dando error y el siguiente informe:

---- Minecraft Crash Report -------- Minecraft Crash Report ----// You're mean.
Time: 27/10/19 10:44 PMDescription: 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.StringBuilder.append(StringBuilder.java:190) at com.google.gson.stream.JsonReader.nextQuotedValue(JsonReader.java:1014) at com.google.gson.stream.JsonReader.nextString(JsonReader.java:815) at com.google.gson.internal.bind.TypeAdapters$16.read(TypeAdapters.java:418) at com.google.gson.internal.bind.TypeAdapters$16.read(TypeAdapters.java:406) at com.google.gson.internal.bind.TypeAdapterRuntimeTypeWrapper.read(TypeAdapterRuntimeTypeWrapper.java:41) at com.google.gson.internal.bind.CollectionTypeAdapterFactory$Adapter.read(CollectionTypeAdapterFactory.java:82) at com.google.gson.internal.bind.CollectionTypeAdapterFactory$Adapter.read(CollectionTypeAdapterFactory.java:61) at zs.a(SourceFile:505) at zs.a(SourceFile:513) at zs.a(SourceFile:528) at cyg.a(SourceFile:369) 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.StringBuilder.append(StringBuilder.java:190) at com.google.gson.stream.JsonReader.nextQuotedValue(JsonReader.java:1014) at com.google.gson.stream.JsonReader.nextString(JsonReader.java:815) at com.google.gson.internal.bind.TypeAdapters$16.read(TypeAdapters.java:418) at com.google.gson.internal.bind.TypeAdapters$16.read(TypeAdapters.java:406) at com.google.gson.internal.bind.TypeAdapterRuntimeTypeWrapper.read(TypeAdapterRuntimeTypeWrapper.java:41) at com.google.gson.internal.bind.CollectionTypeAdapterFactory$Adapter.read(CollectionTypeAdapterFactory.java:82) at com.google.gson.internal.bind.CollectionTypeAdapterFactory$Adapter.read(CollectionTypeAdapterFactory.java:61) at zs.a(SourceFile:505) at zs.a(SourceFile:513) at zs.a(SourceFile:528) at cyg.a(SourceFile:369) 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 7 (amd64) version 6.1 Java Version: 1.8.0_51, Oracle Corporation Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation Memory: 989000992 bytes (943 MB) / 2728919040 bytes (2602 MB) up to 2863661056 bytes (2731 MB) CPUs: 4 JVM Flags: 3 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xss1M -Xmx3G 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>

Try an updated Java instead of the Minecraft's buit in Java.

You'll need to manually update the Java version in the launcher if you've installed a higher version on the PC.

I'm not sure of the exact cause of this but it is a fairly common issue, and appears to be linked to reading a JSON file, perhaps an invalid or corrupted file which is making the game attempt to allocate gigabytes of memory all at once (the second report shows that there is 943 MB used out of 2731 MB and I've seen this happen with even >8 GB allocated).

Note that before doing a complete reinstallation try deleting the "options.txt" file from the .minecraft folder, which has been reported to fix the issue (it is very, very unlikely that the actual game files are corrupted unless it is a modded version as the launcher verifies the integrity of all files except for data files on every launch. This includes options.txt/other configuration files, mods, resource packs, data packs, and saves, any of which could cause the game to crash but aren't due to an error in the game itself (aside from not having safeguards in place to prevent corrupt data from crashing it).