MC-130424Stack overflow after opening a 18w21b world in 18w22a
I have a server running 18w21b. I updated it to 18w22a and the server crashes as soon as a player joins. Attached are the crash reports.
Description: Exception ticking world java.lang.StackOverflowError: Exception ticking world at it.unimi.dsi.fastutil.longs.Long2ObjectMaps$SynchronizedMap.get(Long2ObjectMaps.java:448) at sk.a(SourceFile:81) at sk.b(SourceFile:110) at sk.c(SourceFile:120) at bbf.d(SourceFile:248) at bbf.l(SourceFile:243) at bbf.a_(SourceFile:588) at bis.b(SourceFile:72) at bis.a(SourceFile:64) at bod.a(SourceFile:229) at bfu.a(SourceFile:204) at bod.a(SourceFile:177) at bbf.a(SourceFile:304) at bfu.a(SourceFile:235) at bfu.a(SourceFile:205) at bod.a(SourceFile:177) at bbf.a(SourceFile:304) at bfu.a(SourceFile:235) at bfu.a(SourceFile:205)
Linked Issues
Created Issue:
Server crash after updating to 18w22a
Environment
I have a server running 18w21b. I updated it to 18w22a and the server crashes as soon as a player joins. Attached are the crash reports.
![[Bot] Arisa](../../../data/assets/gravatar/mustek2.png){kind=small}
I have a server running 18w21b. I updated it to 18w22a and the server crashes as soon as a player joins. Attached are the crash reports.
I have a server running 18w21b. I updated it to 18w22a and the server crashes as soon as a player joins. Attached are the crash reports.
I have a server running 18w21b. I updated it to 18w22a and the server crashes as soon as a player joins. Attached are the crash reports.
Description: Exception ticking world java.lang.StackOverflowError: Exception ticking world at it.unimi.dsi.fastutil.longs.Long2ObjectMaps$SynchronizedMap.get(Long2ObjectMaps.java:448) at sk.a(SourceFile:81) at sk.b(SourceFile:110) at sk.c(SourceFile:120) at bbf.d(SourceFile:248) at bbf.l(SourceFile:243) at bbf.a_(SourceFile:588) at bis.b(SourceFile:72) at bis.a(SourceFile:64) at bod.a(SourceFile:229) at bfu.a(SourceFile:204) at bod.a(SourceFile:177) at bbf.a(SourceFile:304) at bfu.a(SourceFile:235) at bfu.a(SourceFile:205) at bod.a(SourceFile:177) at bbf.a(SourceFile:304) at bfu.a(SourceFile:235) at bfu.a(SourceFile:205)
is duplicated by
duplicates
is duplicated by
duplicates
is duplicated by
is duplicated by
Server crash after updating to18w22aStack overflow after opening a 18w21b world in 18w22a
is duplicated by
![[Mod] Neko](../../../data/avatars/users/92901.png){kind=small}
is duplicated by
is duplicated by
![[Mojang] Georgii Gavrichev](../../../data/avatars/users/22428.png){kind=small}
[Mojang] Georgii GavrichevSeems similar to what I experienced #MC-130424
Vararu Rares, this are more than one issue:
1. Broken resource pack:
... 11 more
19:15:20 ui Client thread Couldn't find pack meta for pack file/Ragecraft Faithful 64x64.zip
19:15:20 tq Client thread Couldn't load pack metadata
com.google.gson.JsonSyntaxException: com.google.gson.stream.MalformedJsonException: Invalid escape sequence at line 4 column 38 path $.pack.description
at com.google.gson.internal.Streams.parse(Streams.java:60)
at com.google.gson.JsonParser.parse(JsonParser.java:84)
at com.google.gson.JsonParser.parse(JsonParser.java:59)
at tq.a(SourceFile:72)
at tq.a(SourceFile:65)
at ui.a(SourceFile:35)
2. MC-130424
Dennis Ewell MC-130431 was wrongly linked here, in fact it's a duplicate of MC-130424
This is a known crash caused by upgrading a world created in 18w21b to 18w22a. See MC-130424.
That was MC-130424.
I can't attach the crash report, but I too just had the problem.
It happened when I tried joining a chunk that was not part of the spawn chunks. Nether was fine though.
It keeps repeating the same class files
so it seems like it's an infinite recursion loop.
This is NOT resolved by a longshot - I keep getting a Connection Closed disconnected on a single player game - are these even test launched a LITTLE before throwing a new snapshot into the wild? Seriously lame to release a snapshot the destroys a previous world irrevocably - i know the disclaimer ... but still - just about EVERY TESTER just lost their world ...
James Rood, this ticket isn't resolved. Also, you should save backups of your worlds before updating.
I'm seeing the same thing, though the world worked just fine while working on a witch farm away from spawn but after coming out of the Nether near spawn the exception occurs. World: https://drive.google.com/file/d/1v0-ili6QtRV3USdUgF6jGBSu7kPbMLzN/view?usp=sharing
This fixed my login issue! Thanks guys for your hard work wrangling the bugs!