Robert Byrn

Another correction: The mere act of entering another dimension causes this issue. And after several tests, I can also confirm that you do get shunted one block to the left of your bed. This is absolutely bizarre. 

Ok, so this seems to be tied up with the Nether. If I enter the Nether and then die, the bed bugs out and locks me into an eternal sleep until I relog. Also, it appears that I get shunted one block to the left of the bed during the animation. Again, what the heck?

That is weird. Normally, Java downloads the appropriate version automatically.

Did it help at all? 

Dawid: Did you add the -Xss1024K or -Xss1M argument into the JVM arguments box?

For some reason, this problem occurs because either Minecraft or Java defaults the stack size to the 32-bit default, which is 320K, when the game requires–at minimum in it's current state–640K stack size. So, in order to get the game to run, we have to force the JVM to utilize at least the 640K stack size, preferably 1024K for stability purposes.

This is why we need to add the -Xss1024K tag in the JVM arguments: it will force the game to allocate that much stack space, eliminating the stack verions of an Out of Memory error.

I'm glad to here that everybody's back to having fun with the new snapshots! 

@Ray Allen-- You're welcome! And that is just bizarre, considering that 1024K is the 64-bit stack default.

@[Mod]Pokechu22-- I was just messing around with it after the 1024K modifier locked my game up trying to save and quit. At 640, I was able to save without issue, but the launcher crashed upon exiting. I'll play around some more at 1024 to see if the lock up occurs again. 

Sorry, Kumasasa, but I have another edit for you. I've been messing around with the -Xss parameter in the launcher, and got the snapshots working at as little as 640K for stack size. 

Thanks! I'm glad I can help!

Also, you might want to change those G's to M's. We don't want to fry any processors by adding more stacks than they can support, now do we?

Guys, I've just hit a workaround for the crashing issues.

In your launcher, go under the JVM arguments for the snapshots, and at the very end, add this argument:

-Xss1024K

This will increase the stack size and allow you to start running the new snapshots.

Let's add 18w20c to the list of affected versions.

That's the thing: Minecraft would've thrown a java.lang.OutofMemory error if that was the case. Also, ShelLuser tested various memory set ups, and got no results. I can also run Forge mods–some fairly heavy-- on 1G RAM and they run just fine, if slow due to constant garbage collection. And another thing: We all were able to run 18w16a, which means our hardware setups can handle 1.13 when it comes out. But something went seriously wrong when updating to 18w19a+, resulting in in inability to even load the loading screen.

Looks like we need to add 18w20b to the list of affected versions. Also, the launcher now crashes without adding the errors to the launcher log when you enable the "Open Output Log" option.

It would appear to be a 32-bit issue. I follow Xisumavoid on YouTube, as well as a few other Hermits, and they seem to be able to load the snapshots perfectly. Seriously, Xisumavoid just put out a video highlighting the new 18w20a snapshots a few hours ago.

 Edit: I'm also running 32-bit Java on Windows 10. I've also reverted to Java SE 8 Update 111, and still got the same crash. 

I'm having this issue as well (MC-129599). The launcher log shows that this is due to the game being unable to bootstrap its datafixers, resulting in a StackOverflowError.