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
is duplicated by
relates to
Attachments
Comments

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

Yes Official Laucher

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.
Does this happen in 1.13.1?

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?

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

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

Confirmed in 1.13.2.

-Xmx2G also fixes it

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

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

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.

Confirmed for 18w43a.

yes this affects versions 1.13.2 forward

Affects for 18w43b.

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

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...

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

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.

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

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

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

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

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

The same for Windows Vista (x32) users!

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

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

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

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

sounds like MC-138093 then

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. :-/

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)

Confirmed for 18w45a.

Confirmed for 18w46a

Confirmed for 18w47a.

Confirmed for 18w47b. Fix this weekend?
Don't get your hopes up. The developers don't work on weekends. Weekends are weekends, after all.

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. :-/

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.

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

Confirmed for 18w48a.

Confirmed for 18w49a.

Confirmed for 18w50a

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

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

Confirmed for 19w02a

And 19w03a too

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)

19w03b and 19w03c the same.

19w04a and 19w04b affected too

19w05a and 19w06a too

19w07a this too!

Let me add 19w08a

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.

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

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.
@unknown, please create a new ticket if the issue persists.