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
is duplicated by 5
Attachments
Comments 6
It keeps repeating the same class files
at bbf.a(SourceFile:304)
at bfu.a(SourceFile:235)
at bfu.a(SourceFile:205)
at bod.a(SourceFile:177)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 ...
@unknown, 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!
Fry
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.