mojira.dev
MC-131071

New Chunk generation Exception: Asking a region for a chunk out of bound | X X

Players when loading different regions in the world will cause the generation to ask for a region out of bounds, immediately crashing the server. When loading the server again, the server will operate as normal until the triggering player joins again, prompting a crash. Currently in game work around involves having an admin teleport the player away from the triggering area before the crash (Typically a repeating command block teleport command). Attached to this report are several crash reports indicating different locations in the world that are causing the error. Appears to be several chunks.

 This may be related to MC-118106 and is similar in nature to MC-125134

Description: Exception generating new chunk

java.util.concurrent.ExecutionException: java.lang.RuntimeException: We are asking a region for a chunk out of bound | -174 8
	at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357)
	at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1895)
	at sl.c(SourceFile:126)
	at st.a(SourceFile:84)
	at su.c(SourceFile:143)
	at sm.i_(SourceFile:223)
	at net.minecraft.server.MinecraftServer.w(SourceFile:693)
	at rx.w(SourceFile:365)
	at net.minecraft.server.MinecraftServer.v(SourceFile:626)
	at net.minecraft.server.MinecraftServer.run(SourceFile:531)
	at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.RuntimeException: We are asking a region for a chunk out of bound | -174 8
	at sr.c(SourceFile:114)
	at bqc.a(SourceFile:56)
	at sy.a(SourceFile:13)
	at sz.a(SourceFile:34)
	at bqg.a(SourceFile:95)
	at tg.a(SourceFile:62)
	at tg.a(SourceFile:25)
	at agk$a.a(SourceFile:131)
	at java.util.concurrent.CompletableFuture.uniApply(CompletableFuture.java:602)
	at java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:577)
	at java.util.concurrent.CompletableFuture$Completion.exec(CompletableFuture.java:443)
	at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289)
	at java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1056)
	at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1692)
	at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:157)
-- Chunk to be generated --
Details:
	Location: -174,8
	Position hash: 38654705490
	Generator: brx@4ff48f11
Stacktrace:
	at sl.a(SourceFile:170)
	at sl.c(SourceFile:129)
	at st.a(SourceFile:84)
	at su.c(SourceFile:143)
	at sm.i_(SourceFile:223)
	at net.minecraft.server.MinecraftServer.w(SourceFile:693)
	at rx.w(SourceFile:365)
	at net.minecraft.server.MinecraftServer.v(SourceFile:626)
	at net.minecraft.server.MinecraftServer.run(SourceFile:531)
	at java.lang.Thread.run(Thread.java:748)

Linked issues

MC-134415 Game Crashing while trying get in boat Resolved MC-135488 Game Crash Everytime Upon Opening World Resolved MC-135570 The game crashed whilst exception generating new chunk Resolved MC-135587 Exception Generating New Chunks Resolved MC-135826 Exception generating new chunk Resolved

Attachments

Comments 48

This is still a problem in 1.13 PRE-5.

Still an issue in 1.13-pre7, happened when I converted a beta world to 1.13 and then started to explore new chunks.

If remove some corresponding region files, the problem won't happen again.

Can you provide steps to reproduce e.g. a world file with coordinates where it happens? My world does not crash at chunk coordinates -174, 8 (around -2784, 128 block coords)

It is not specific these coördinates everywhere, I am on a server where there are tons of bad chunks that makes the server crash.

38 more comments

Thanks for the help Neko.

Here's the zipped copy of my save. I'm like 90% sure this is what you need. 

 

https://drive.google.com/file/d/18q3vRDzDy45BR0Z9QUyIXqK3iwnnw2jV/view?usp=sharing

That's about everything, though it seems like the file "level.dat" is missing. Is it in the world save? If so, can you attach it here?

Done. Yeah, it's in the world save. 

After much testing, another mod and I came to the conclusion that this is fixed in 18w43a (first 1.14 snapshot). All of the worlds here (with the exception of one) only crash in 1.13.2 and will load in 18w43a and above. Unfortunately, some worlds seem to have corruption issues where chunks are swapped around in both 1.13.2 and 1.14. Example:

Chunk file at [-3, 43] is in the wrong location; relocating. (Expected [-3, 43], got [-1, 43])

Nonetheless, the world does load.

I mentioned "with the exception of one" because one of the worlds provided was once in a modded environment and led us to believe that this was still an issue in 1.14 (hence why some of the 1.14 snapshots are mistakenly listed in the affected versions).

If you can still reproduce this crash in the latest version (meaning 1.14 and up), please create a new ticket with the world download attached or linked.

Thanks Neko. This means with the update on Tuesday, this should be taken care of?

Joshua VanDeVelde

(Unassigned)

Confirmed

Chunk loading, Crash

crash, multiplayer, server, world-generation

Minecraft 1.13-pre1, Minecraft 1.13-pre5, Minecraft 1.13-pre7, Minecraft 1.13-pre8, Minecraft 1.13, ..., Minecraft 19w12a, Minecraft 19w12b, Minecraft 19w13b, Minecraft 19w14a, Minecraft 19w14b

Minecraft 18w43a

Retrieved