mojira.dev
MC-137353

Game runs out of memory while building datafixers

Workaround

Add -Xss320k or -Xmx2G to your JVM arguments.

Usually happens in 32 bit systems only

16:39:27	launcher	Preparing to launch minecraft client for 1.13.2-pre2
16:39:29	launcher	Checking installations.
16:39:29	launcher	Minecraft client 1.13.2-pre2 is ready to start.
16:39:29	launcher	Starting!
16:39:29	launcher	Using default game log configuration client-1.12.xml (outputs XML)
16:39:34	cft	Setting user: KairoMartins18
13:39:47	game	Exception in thread "Client thread" java.lang.OutOfMemoryError: unable to create new native thread
	at java.lang.Thread.start0(Native Method)
	at java.lang.Thread.start(Thread.java:714)
	at java.util.concurrent.CompletableFuture$ThreadPerTaskExecutor.execute(CompletableFuture.java:405)
	at java.util.concurrent.CompletableFuture.asyncRunStage(CompletableFuture.java:1632)
	at java.util.concurrent.CompletableFuture.runAsync(CompletableFuture.java:1850)
	at com.mojang.datafixers.DataFixerBuilder.build(DataFixerBuilder.java:70)
	at xz.b(SourceFile:140)
	at xz.<clinit>(SourceFile:135)
	at aev$a.a(SourceFile:445)
	at aev.a(SourceFile:131)
	at aev.<clinit>(SourceFile:137)
	at pf.c(SourceFile:470)
	at cft.<init>(SourceFile:370)
	at net.minecraft.client.main.Main.main(SourceFile:144)
  <log4j:Event logger="com.mojang.datafixers.DataFixerBuilder" timestamp="1539977987406" level="ERROR" thread="Thread-571">
    <log4j:Message><![CDATA[Unable to build datafixers]]></log4j:Message>
    <log4j:Throwable><![CDATA[java.util.concurrent.CompletionException: java.lang.BootstrapMethodError: call site initialization exception
	at java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:273)
	at java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:280)
	at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1621)
	at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.BootstrapMethodError: call site initialization exception
	at java.lang.invoke.CallSite.makeSite(CallSite.java:341)
	at java.lang.invoke.MethodHandleNatives.linkCallSiteImpl(MethodHandleNatives.java:307)
	at java.lang.invoke.MethodHandleNatives.linkCallSite(MethodHandleNatives.java:297)
	at aap.makeRule(SourceFile:31)
	at com.mojang.datafixers.DataFix.getRule(DataFix.java:97)
	at com.mojang.datafixers.DataFixerUpper.lambda$getRule$6(DataFixerUpper.java:136)
	at com.mojang.datafixers.DataFixerUpper$$Lambda$394/5578326.apply(Unknown Source)
	at java.util.Map.computeIfAbsent(Map.java:957)
	at it.unimi.dsi.fastutil.longs.Long2ObjectMap.computeIfAbsent(Long2ObjectMap.java:606)
	at it.unimi.dsi.fastutil.longs.Long2ObjectMaps$SynchronizedMap.computeIfAbsent(Long2ObjectMaps.java:530)
	at it.unimi.dsi.fastutil.longs.Long2ObjectMaps$SynchronizedMap.computeIfAbsent(Long2ObjectMaps.java:295)
	at com.mojang.datafixers.DataFixerUpper.getRule(DataFixerUpper.java:131)
	at com.mojang.datafixers.DataFixerBuilder.lambda$build$1(DataFixerBuilder.java:72)
	at com.mojang.datafixers.DataFixerBuilder$$Lambda$382/2455707.run(Unknown Source)
	at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1618)
	... 1 more
Caused by: java.lang.OutOfMemoryError: Metaspace
]]></log4j:Throwable>
  </log4j:Event>
13:39:47	monitor	expected <
16:39:43	com.mojang.datafixers.DataFixerBuilder	Unable to build datafixers
java.util.concurrent.CompletionException: java.lang.BootstrapMethodError: call site initialization exception
	at java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:273)
	at java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:280)
	at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1621)
	at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.BootstrapMethodError: call site initialization exception
	at java.lang.invoke.CallSite.makeSite(CallSite.java:341)
	at java.lang.invoke.MethodHandleNatives.linkCallSiteImpl(MethodHandleNatives.java:307)
	at java.lang.invoke.MethodHandleNatives.linkCallSite(MethodHandleNatives.java:297)
	at aap.makeRule(SourceFile:31)
	at com.mojang.datafixers.DataFix.getRule(DataFix.java:97)
	at com.mojang.datafixers.DataFixerUpper.lambda$getRule$6(DataFixerUpper.java:136)
	at com.mojang.datafixers.DataFixerUpper$$Lambda$394/5578326.apply(Unknown Source)
	at java.util.Map.computeIfAbsent(Map.java:957)
	at it.unimi.dsi.fastutil.longs.Long2ObjectMap.computeIfAbsent(Long2ObjectMap.java:606)
	at it.unimi.dsi.fastutil.longs.Long2ObjectMaps$SynchronizedMap.computeIfAbsent(Long2ObjectMaps.java:530)
	at it.unimi.dsi.fastutil.longs.Long2ObjectMaps$SynchronizedMap.computeIfAbsent(Long2ObjectMaps.java:295)
	at com.mojang.datafixers.DataFixerUpper.getRule(DataFixerUpper.java:131)
	at com.mojang.datafixers.DataFixerBuilder.lambda$build$1(DataFixerBuilder.java:72)
	at com.mojang.datafixers.DataFixerBuilder$$Lambda$382/2455707.run(Unknown Source)
	at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1618)
	... 1 more
Caused by: java.lang.OutOfMemoryError: Metaspace
	at sun.misc.Unsafe.defineAnonymousClass(Native Method)
	at java.lang.invoke.InnerClassLambdaMetafactory.spinInnerClass(InnerClassLambdaMetafactory.java:324)
	at java.lang.invoke.InnerClassLambdaMetafactory.buildCallSite(InnerClassLambdaMetafactory.java:194)
	at java.lang.invoke.LambdaMetafactory.metafactory(LambdaMetafactory.java:304)
	at java.lang.invoke.LambdaForm$DMH/31016500.invokeStatic_L6_L(LambdaForm$DMH)
	at java.lang.invoke.LambdaForm$BMH/24567020.reinvoke(LambdaForm$BMH)
	at java.lang.invoke.LambdaForm$MH/11902257.invoke_MT(LambdaForm$MH)
	at java.lang.invoke.CallSite.makeSite(CallSite.java:302)
	... 15 more
16:39:44	com.mojang.datafixers.DataFixerBuilder	Unable to build datafixers
java.util.concurrent.CompletionException: java.lang.BootstrapMethodError: call site initialization exception
	at java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:273)
	at java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:280)
	at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1621)
	at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.BootstrapMethodError: call site initialization exception
	at java.lang.invoke.CallSite.makeSite(CallSite.java:341)
	at java.lang.invoke.MethodHandleNatives.linkCallSiteImpl(MethodHandleNatives.java:307)
	at java.lang.invoke.MethodHandleNatives.linkCallSite(MethodHandleNatives.java:297)
	at aap.makeRule(SourceFile:31)
	at com.mojang.datafixers.DataFix.getRule(DataFix.java:97)
	at com.mojang.datafixers.DataFixerUpper.lambda$getRule$6(DataFixerUpper.java:136)
	at com.mojang.datafixers.DataFixerUpper$$Lambda$394/5578326.apply(Unknown Source)
	at java.util.Map.computeIfAbsent(Map.java:957)
	at it.unimi.dsi.fastutil.longs.Long2ObjectMap.computeIfAbsent(Long2ObjectMap.java:606)
	at it.unimi.dsi.fastutil.longs.Long2ObjectMaps$SynchronizedMap.computeIfAbsent(Long2ObjectMaps.java:530)
	at it.unimi.dsi.fastutil.longs.Long2ObjectMaps$SynchronizedMap.computeIfAbsent(Long2ObjectMaps.java:295)
	at com.mojang.datafixers.DataFixerUpper.getRule(DataFixerUpper.java:131)
	at com.mojang.datafixers.DataFixerBuilder.lambda$build$1(DataFixerBuilder.java:72)
	at com.mojang.datafixers.DataFixerBuilder$$Lambda$382/2455707.run(Unknown Source)
	at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1618)
	... 1 more
Caused by: java.lang.OutOfMemoryError: Metaspace
	at sun.misc.Unsafe.defineAnonymousClass(Native Method)
	at java.lang.invoke.InnerClassLambdaMetafactory.spinInnerClass(InnerClassLambdaMetafactory.java:324)
	at java.lang.invoke.InnerClassLambdaMetafactory.buildCallSite(InnerClassLambdaMetafactory.java:194)
	at java.lang.invoke.LambdaMetafactory.metafactory(LambdaMetafactory.java:304)
	at java.lang.invoke.LambdaForm$DMH/31016500.invokeStatic_L6_L(LambdaForm$DMH)
	at java.lang.invoke.LambdaForm$BMH/24567020.reinvoke(LambdaForm$BMH)
	at java.lang.invoke.LambdaForm$MH/11902257.invoke_MT(LambdaForm$MH)
	at java.lang.invoke.CallSite.makeSite(CallSite.java:302)
	... 15 more
16:39:44	com.mojang.datafixers.DataFixerBuilder	Unable to build datafixers
java.util.concurrent.CompletionException: java.lang.BootstrapMethodError: call site initialization exception
	at java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:273)
	at java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:280)
	at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1621)
	at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.BootstrapMethodError: call site initialization exception
	at java.lang.invoke.CallSite.makeSite(CallSite.java:341)
	at java.lang.invoke.MethodHandleNatives.linkCallSiteImpl(MethodHandleNatives.java:307)
	at java.lang.invoke.MethodHandleNatives.linkCallSite(MethodHandleNatives.java:297)
	at aap.makeRule(SourceFile:31)
	at com.mojang.datafixers.DataFix.getRule(DataFix.java:97)
	at com.mojang.datafixers.DataFixerUpper.lambda$getRule$6(DataFixerUpper.java:136)
	at com.mojang.datafixers.DataFixerUpper$$Lambda$394/5578326.apply(Unknown Source)
	at java.util.Map.computeIfAbsent(Map.java:957)
	at it.unimi.dsi.fastutil.longs.Long2ObjectMap.computeIfAbsent(Long2ObjectMap.java:606)
	at it.unimi.dsi.fastutil.longs.Long2ObjectMaps$SynchronizedMap.computeIfAbsent(Long2ObjectMaps.java:530)
	at it.unimi.dsi.fastutil.longs.Long2ObjectMaps$SynchronizedMap.computeIfAbsent(Long2ObjectMaps.java:295)
	at com.mojang.datafixers.DataFixerUpper.getRule(DataFixerUpper.java:131)
	at com.mojang.datafixers.DataFixerBuilder.lambda$build$1(DataFixerBuilder.java:72)
	at com.mojang.datafixers.DataFixerBuilder$$Lambda$382/2455707.run(Unknown Source)
	at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1618)
	... 1 more
Caused by: java.lang.OutOfMemoryError: Metaspace
	at sun.misc.Unsafe.defineAnonymousClass(Native Method)
	at java.lang.invoke.InnerClassLambdaMetafactory.spinInnerClass(InnerClassLambdaMetafactory.java:324)
	at java.lang.invoke.InnerClassLambdaMetafactory.buildCallSite(InnerClassLambdaMetafactory.java:194)
	at java.lang.invoke.LambdaMetafactory.metafactory(LambdaMetafactory.java:304)
	at java.lang.invoke.LambdaForm$DMH/31016500.invokeStatic_L6_L(LambdaForm$DMH)
	at java.lang.invoke.LambdaForm$BMH/24567020.reinvoke(LambdaForm$BMH)
	at java.lang.invoke.LambdaForm$MH/11902257.invoke_MT(LambdaForm$MH)
	at java.lang.invoke.CallSite.makeSite(CallSite.java:302)
	... 15 more
16:39:43	com.mojang.datafixers.DataFixerBuilder	Unable to build datafixers
java.util.concurrent.CompletionException: java.lang.BootstrapMethodError: call site initialization exception
	at java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:273)
	at java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:280)
	at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1621)
	at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.BootstrapMethodError: call site initialization exception
	at java.lang.invoke.CallSite.makeSite(CallSite.java:341)
	at java.lang.invoke.MethodHandleNatives.linkCallSiteImpl(MethodHandleNatives.java:307)
	at java.lang.invoke.MethodHandleNatives.linkCallSite(MethodHandleNatives.java:297)
	at aap.makeRule(SourceFile:31)
	at com.mojang.datafixers.DataFix.getRule(DataFix.java:97)
	at com.mojang.datafixers.DataFixerUpper.lambda$getRule$6(DataFixerUpper.java:136)
	at com.mojang.datafixers.DataFixerUpper$$Lambda$394/5578326.apply(Unknown Source)
	at java.util.Map.computeIfAbsent(Map.java:957)
	at it.unimi.dsi.fastutil.longs.Long2ObjectMap.computeIfAbsent(Long2ObjectMap.java:606)
	at it.unimi.dsi.fastutil.longs.Long2ObjectMaps$SynchronizedMap.computeIfAbsent(Long2ObjectMaps.java:530)
	at it.unimi.dsi.fastutil.longs.Long2ObjectMaps$SynchronizedMap.computeIfAbsent(Long2ObjectMaps.java:295)
	at com.mojang.datafixers.DataFixerUpper.getRule(DataFixerUpper.java:131)
	at com.mojang.datafixers.DataFixerBuilder.lambda$build$1(DataFixerBuilder.java:72)
	at com.mojang.datafixers.DataFixerBuilder$$Lambda$382/2455707.run(Unknown Source)
	at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1618)
	... 1 more
Caused by: java.lang.OutOfMemoryError: Metaspace
	at sun.misc.Unsafe.defineAnonymousClass(Native Method)
	at java.lang.invoke.InnerClassLambdaMetafactory.spinInnerClass(InnerClassLambdaMetafactory.java:324)
	at java.lang.invoke.InnerClassLambdaMetafactory.buildCallSite(InnerClassLambdaMetafactory.java:194)
	at java.lang.invoke.LambdaMetafactory.metafactory(LambdaMetafactory.java:304)
	at java.lang.invoke.LambdaForm$DMH/31016500.invokeStatic_L6_L(LambdaForm$DMH)
	at java.lang.invoke.LambdaForm$BMH/24567020.reinvoke(LambdaForm$BMH)
	at java.lang.invoke.LambdaForm$MH/11902257.invoke_MT(LambdaForm$MH)
	at java.lang.invoke.CallSite.makeSite(CallSite.java:302)
	... 15 more
16:39:46	com.mojang.datafixers.DataFixerBuilder	Unable to build datafixers
java.util.concurrent.CompletionException: java.lang.BootstrapMethodError: call site initialization exception
	at java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:273)
	at java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:280)
	at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1621)
	at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.BootstrapMethodError: call site initialization exception
	at java.lang.invoke.CallSite.makeSite(CallSite.java:341)
	at java.lang.invoke.MethodHandleNatives.linkCallSiteImpl(MethodHandleNatives.java:307)
	at java.lang.invoke.MethodHandleNatives.linkCallSite(MethodHandleNatives.java:297)
	at aap.makeRule(SourceFile:31)
	at com.mojang.datafixers.DataFix.getRule(DataFix.java:97)
	at com.mojang.datafixers.DataFixerUpper.lambda$getRule$6(DataFixerUpper.java:136)
	at com.mojang.datafixers.DataFixerUpper$$Lambda$394/5578326.apply(Unknown Source)
	at java.util.Map.computeIfAbsent(Map.java:957)
	at it.unimi.dsi.fastutil.longs.Long2ObjectMap.computeIfAbsent(Long2ObjectMap.java:606)
	at it.unimi.dsi.fastutil.longs.Long2ObjectMaps$SynchronizedMap.computeIfAbsent(Long2ObjectMaps.java:530)
	at it.unimi.dsi.fastutil.longs.Long2ObjectMaps$SynchronizedMap.computeIfAbsent(Long2ObjectMaps.java:295)
	at com.mojang.datafixers.DataFixerUpper.getRule(DataFixerUpper.java:131)
	at com.mojang.datafixers.DataFixerBuilder.lambda$build$1(DataFixerBuilder.java:72)
	at com.mojang.datafixers.DataFixerBuilder$$Lambda$382/2455707.run(Unknown Source)
	at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1618)
	... 1 more
Caused by: java.lang.OutOfMemoryError: Metaspace

Related issues

MC-10126 Sheep aren't fully invisible? MC-10131 Difficult inventory management MC-10145 Wheat seeds can not be placed normally, "pops out" MC-10357 Getting into a minecart with a mob in it crashes minecraft MC-10490 When using the /effect command for Instant Healing (not sure if this is intended), players will glitch in lava and loose all their hunger MC-137416 Minecraft crashes before it loads MC-137435 Minecraft does not start in version 1.13.2 MC-137436 An unexpected issue occurred after update to version 1.13 MC-137444 process crashed with exit code 1 MC-137590 Process crashed with exit code 1 MC-137634 Minecraft Server won't start: "java.lang.OutOfMemoryError: unable to create new native thread" MC-137636 bug with running 18w43b snapshot MC-137796 The game does not start after clicking play, it's the error and closes the game by returning to the launch MC-137806 minecraft not launching MC-137919 Cannot run on 32 bit Windows 7 MC-138068 Minecraft Launcher Crash MC-138079 When launching 1.14 snapshots (14w43a/b/c) the game crashes immediately after its launched MC-138085 Crash when game start MC-138156 Game use 100% CPU and close, even i add -Xss320k MC-138157 Game use 100% CPU and close, even i write only -Xss320k in JVM argument MC-138176 1.13.2 unable to open after 1.13.2 MC-138406 Do not open the Minecraft 1.13.2 forward. MC-138441 Process crashed with exit code 1 MC-138636 Out of memory in 32bit MC-138732 I cant launch my minecraft help MC-138769 Can't start Minecraft Version 1.13.2 MC-138840 Error: Game runs out of memory 1.13.2, 1.13.1 it's running. MC-138877 Mincraft crashs when starting 1.13.2 or later snapshots MC-138925 The launcher don't load since Octuber 22 MC-138940 Cannot play snapshot MC-139531 Can't play any 1.14 snapshots MC-140341 I can't start my world first version MC-140630 Snapshot Crash MC-140631 Snapshot Crashes every time. MC-141124 Process crahsed with exit code 1 MC-142323 Minecraft crashes upon launching (Above 1.13.2) MC-142967 Minecraft 19w04a snapshot doens't works MC-175872 Exit code 1 MCL-10126 Launch error 1.13.2 MCL-10129 When I open launcher and hit play on latest version 1.13.2 it crashes MCL-10131 The Launcher keeps crashing MCL-10145 Game Crash when i tried to update to 1.13.2 MCL-10357 Launcher crashes when I start snapshots (Only snapshots)

Attachments

Comments

migrated
[media]
Asteraoth

Are you using the official launcher from https://minecraft.net/en-us/download?

migrated

Yes Official Laucher

migrated

Same is happening here. Seems to be a 32-bit problem, as it looks like the error I got when 1.13 snapshots were being released.

[Mod] Neko

Does this happen in 1.13.1?

migrated

Issue fixed. I just added "-Xss320k" to the JVM Arguments and I was able to play it. Maybe the game was trying to use the 1M stack size by default?

migrated

Yes, i think is OutOfMemoryError bug. is 32 bit problem. Please fix it.

migrated

Where abouts do I add the "-Xss320k" in the JVM arguments as mine has "-Xmx1G -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=16M" in allready

migrated

Confirmed in 1.13.2.

Uriel Salischiker

-Xmx2G also fixes it

migrated

harry, erase everything in the JVM Arguments and then add -Xss320k

migrated

the arguments none is working I'm already panicking already the argument -Xss320k worked first time when loading closed is no longer opened nen stable version being the other does not open

migrated

They need to fix it as fast as possible, seems like it happens with every 32-bit users. I wonder why this is happening, its the same thing that happened in 1.13 snapshots.

migrated

Confirmed for 18w43a.

migrated

yes this affects versions 1.13.2 forward

migrated

Affects for 18w43b.

migrated

The arguments didn't work. Confirmed for 1.13.2, 18w43a & 18w43b, hope this get fixed soon...

migrated

My ticket (MC-137634) got marked as duplicate, but I'm not st sure about it. None of the workarounds did work; and it's a 64bit server (running 64bit Java), so I don't think it's 32bit related...

migrated

I keep didn't start at 18w43c, Confirmed for 18w43c.

migrated

The JVM argument -Xss320k allowed the 13.2 update to load instead of instantly crash with an out of memory error (-Xmx2G didn't work). However, the lag is complete (fps 0) and the game freezes and unfreezes constantly and is unplayable. Now, I am warned that I cannot go back to 13.1 since the game's lagging was saved in 13.2. I did save my game before trying the workaround so I am back playing in 13.1.

migrated

there was a small update on 1.13.2 because the argument -Xssx320 voted to work more remains unsustainable can not play

migrated

stop for the outofmemoryerror in the didn't start, 32 bit. Confirmed for 18w44a

migrated

I am from Venezuela, I no have the resource for a new Computer or memory 😞 I use 1 GB RAM for my Minecraft

migrated

Game not run in 1gb of RAM in 32 bit?

migrated

The "-Xmx2G" workaround does not work what so ever and "-Xss320k" JVM argument should not be counted as a workaround... The max fps I can get with Xss320k adds up to a Grand total of 10 and it chugs like a mf every other second. Is there anything else we could do to fix this besides buying a new computer or buying/installing more memory? It seems that Windows 7 (x32) users are being left in the dust as they physically cannot install more than 4 GB of RAM. How 1.13.2 differs so much from 1.13.1 is kinda beyond me but nothing to be done about it. Please help us enjoy your game... Sincerely, People-With-No-Money

migrated

The same for Windows Vista (x32) users!

Uriel Salischiker

1.13.2 updates datafixerupper, which now uses more threads.
The OS runs out of native threads while running on a 32 bit system, thus triggering the Out of memory error

migrated

@Urielsalis: that's weird. In my case it's a 64bit server (See MC-137634). How many "more threads" are there??

Uriel Salischiker

with only 2 cores? And there are thousands of more threads

migrated

Yeah... only 2 cores. That's what one gets when using a "cheap" vServer to save some money.  😉

Uriel Salischiker

sounds like MC-138093 then

migrated

not really... it's still only a server, it has no graphics card and it runs Ubuntu Linux. However, all the components are a little out of date, since this VM host didn't upgrade in the last 5 years.  :-/

Uriel Salischiker

From @marcono1234

It is not documented, but `commonPool()` has available processors -1 (http://hg.openjdk.java.net/jdk8u/jdk8u/jdk/file/478a4add975b/src/share/classes/java/util/concurrent/ForkJoinPool.java#l3435)

And https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/CompletableFuture.html says
> All async methods without an explicit Executor argument are performed using the ForkJoinPool.commonPool() (unless it does not support a parallelism level of at least two, in which case, a new Thread is created to run each task)
And also https://bugs.openjdk.java.net/browse/JDK-8213114, so explicit usage of the `commonPool()` can cause use of thread per task as well

DataFixerUpper uses number of cores - 1, so in 2 core processors the parallelism ends up being 1, so a thread is created for each thread

This makes the OS run out of native threads while running in 32 bits(this bug), and cause a weird crash in 64 bit(MC-138093)

migrated

Confirmed for 18w45a.

migrated

Confirmed for 18w46a

migrated

Confirmed for 18w47a.

migrated

Confirmed for 18w47b. Fix this weekend?

violine1101

Don't get your hopes up. The developers don't work on weekends. Weekends are weekends, after all.

migrated

Yeah, you just took my words out of my brain, Violine!

Try keep in mind that this place is for BUG REPORTS and not for status requests. Keep calm and wait until it might get fixed. At least the bug is CONFIRMED .. and that might mean it is or will be worked on.  🙂

If I understand it correctly, the reason for the reported behaviour is already found. It's not limited to Windows or 32bit OS, since it can also affect a non-GUI 64bit Linux multiplayer server. 

Another thing: yeah, not everybody can afford a new PC to play Minecraft, but sadly this is the way of all things. It's called evolution.  :-/

migrated

not all people have money to buy a new pc really if it is called undeveloped countries there is no money this is not your reality you must have conditions for a new pc think of people yes in fact the best way is to buy a powerful pc more not to our reality.

migrated

the latest snapshots a and 1.13.2 will work on my pc and you?

migrated

Confirmed for 18w48a.

migrated

Confirmed for 18w49a.

migrated

Confirmed for 18w50a

migrated

I have this laptop https://support.hp.com/us-en/document/c05987723 and this error is happening to me as well on 18w50a, apparently is caused by having a dual core CPU from what others on a similar thread have said, the reason is that the method MC is using to create the game threads uses the number of cores -1 which means that if you have a dual core CPU all the threads try to get shoved onto 1 core which doesn't really work obviously. 1.13 doesn't have this issue for me since I guess it doesn't use that method but everything over 1.13.1 does 🙂 So basically I guess everything after 1.13 requires a 4 core CPU at minimum, RIP my $300 I spent a couple of months ago I guess

migrated

Actually, disregard that, I found what the problem was for me, I realized that I was using 32 bit Java and not 64 bit so I downloaded and installed the latest 64 bit Java (191f) and now i18w50a works 😃 Now I just need to get the newest version of forge for this version (if there is any yet) so I can use optifine to get slightly better FPS

migrated

Confirmed for 19w02a

migrated

And 19w03a too

migrated

A new Java update was released, from what I read it was a bug fix, after I installed it 1.13.2 is able to launch.  I tried to launch 18w43s and 19w03a but was unable to do so , 

 

the following was when I tried to run 19w03a

Exception in thread "Client thread" java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method)
at java.lang.Thread.start(Unknown Source)
at java.util.concurrent.CompletableFuture$ThreadPerTaskExecutor.execute(Unknown Source)
at java.util.concurrent.CompletableFuture.asyncRunStage(Unknown Source)
at java.util.concurrent.CompletableFuture.runAsync(Unknown Source)
at com.mojang.datafixers.DataFixerBuilder.build(DataFixerBuilder.java:70)
at zk.b(SourceFile:155)
at zk.<clinit>(SourceFile:150)
at ahg$a.a(SourceFile:493)
at ahg.a(SourceFile:135)
at ahg.<clinit>(SourceFile:141)
at axd.<clinit>(SourceFile:630)
at cnh.<clinit>(SourceFile:12)
at cnc.a(SourceFile:9)
at bqi.k(SourceFile:211)
at bhl.a_(SourceFile:523)
at bqi$a.<init>(SourceFile:394)
at bqi$a.<init>(SourceFile:382)
at bqi.c(SourceFile:66)
at bhm.<clinit>(SourceFile:711)
at fk.D(SourceFile:75)
at fk.a(SourceFile:109)
at java.util.LinkedHashMap$LinkedEntrySet.forEach(Unknown Source)
at fk.<clinit>(SourceFile:108)
at qf.b(SourceFile:484)
at cqe.<init>(SourceFile:381)
at net.minecraft.client.main.Main.main(SourceFile:154)

migrated

19w03b and 19w03c the same.

migrated

19w04a and 19w04b affected too

migrated

19w05a and 19w06a too

migrated

19w07a this too!

migrated

Let me add 19w08a

migrated

Anyone here knows if it was really fixed? i stopped reporting the snapshots because i live in Venezuela and i have several internet problems and i cant join the 19w09a because i cant download it for that.

migrated

Yes it did! 19w09a confirmed, idk the newest but it did!

migrated

I had this issue on my computer on minecraft 1.14 and 1.14.2 With a windows 7 32 bit, i dont believe -Xmx2G is possible, but when i used -Xss320k i got less than 1 fps. My solution was to add Xmx750M, and it runs just a smooth as it did before the issue occured.

violine1101

@unknown, please create a new ticket if the issue persists.

migrated

Fry

Confirmed

OutOfMemory, crash, datafixerupper

Minecraft 1.13.2-pre2, Minecraft 1.13.2, Minecraft 18w43a, Minecraft 18w43b, Minecraft 18w43c, ..., Minecraft 19w04b, Minecraft 19w05a, Minecraft 19w06a, Minecraft 19w07a, Minecraft 19w08a

Minecraft 19w09a

Retrieved