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 MC-135488 Game Crash Everytime Upon Opening World MC-135570 The game crashed whilst exception generating new chunk MC-135587 Exception Generating New Chunks MC-135826 Exception generating new chunk MC-136354 Server crashes while generating new chunks - java.util.concurrent.ExecutionException: We are asking a region for a chunk out of bound MC-136418 Game crashing loading certain chunks MC-136432 Game crashes while loading a world or just after loading the world MC-136832 Game crashes upon re-entering most used world. MC-136891 Map crashes as soon as it loads in MC-136981 Server Crashes When certain players join - java.lang.StackOverflowError MC-137013 Missing large sections of graphics. lots of blue nothing. game crashes. MC-137170 Game crashes within a few seconds MC-137177 Crashes when trying to generate new chunks & optimizing worlds problem MC-137264 my computer restart while playing and now i have an error and cant go back to game again MC-138314 We are asking a region for a chunk out of bound MC-138513 Exception generating new chunk MC-140481 Game crashes a second or two after loading MC-140482 Specific World is crashing MC-141729 World Crashes Saying "We Are Asking a region for a chunk out of bounds" MC-141740 Game crashes when loading my world MC-142330 Opening world causes game crash MC-142802 After a power outtage I can no longer open my save MC-142856 1.13.2 World Crashes Upon loading MC-143510 We are asking a region for a chunk out of bound MC-143802 N/A MC-144361 Minecraft Server Crashing when players join MC-144390 unexpected error has occured MC-144935 When I enter the this world, My game crashes and gets turn off MC-147311 The game is crashing MC-148538 Minecraft World Crashes on loading in. World then has deleted itself from Minecraft Loader MC-151847 crashing game after entering end since new version

Attachments

Comments

tomudding

This is still a problem in 1.13 PRE-5.

Greg Milson

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

IceLocke

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

NeunEinser

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)

Obi Gysels

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.

DrexHD

World: http://www.mediafire.com/file/upgv34y8kjfqs3b/broken-chunk.zip/file

At coordinates 8440780 | 78 | 6624001

In single and multiplayer

Version: 1.13 pre8

 

tomudding

Does indeed still occur in 1.13 PRE-8. I don't have a world download, but just teleporting to 'high' coordinates causes the game to crash.

ReduxPL

I did some testing on this issue, this is what I have found out:

  • The closest I was able to get the issue to start happening was after I passed the X coordinate of 8.388.455. Thus, the closest chunk I crashed on was at "524290,10". Which is close to 524288. Isn't 524288 = 512 Kib? Maybe that's a valuable clue? 

  • The crashes happen even on a world generated on 1.13-pre8.

  • The issue is present in the latest version of Java 8, and also Java 10.

Basically, to recreate the issue yourself:

  1. Create a new world (in 1.13-pre8, ofc)

  2. /tp @s 8388455 ~ ~

  3. Start moving towards positive X. You should crash in around a minute of travelling, probably depending on your render distance.

 

EDIT: Collected some more info:

  • The crashes occur only when at least one of the coordinates exceeds the value above. If you travel the same amount of blocks diagonally (eg. to X: 5.000.000 | Z: 5.000.000), crashes do not occur.

  • When done on the same world seed, it will always be the same chunks that cause the crash.

  • Structure generating set to "off" does not seem to make the difference.

tomudding

Can confirm what @ReduxPL said for 1.13 PRE-9.

tomudding

Still crashing the game in 1.13 PRE-10.

tomudding

Can confirm for 1.13.

John Spanos

Can confirm for 1.13.  Attached crash report: 

[media]

 

Note, that this is not a chunk with a large coordinate value.  The crash happens when a player loads chunks from position 638, 71, 2254.  Nowhere near out of bounds for these coordinates.  

Alex Darlow

Edit: My issue was actually MC-125134 and was fixed in 18w30a snapshot.

Nikita

Can confirm for 1.13, 18w30b and 18w31a

 

[media][media][media]

Crash logs attatched

Nick Anderson

I am having the same issue on 1.13.  Seems the issue started when my PC unexpectedly shutdown.  I happened to be in water at the time and sinking, so not sure if that has anything to do with it or if the chunk data was just corrupted after the power loss.

[media]
Seth Howell

My server is having the same issue - and now it's very pointless for anyone to play since it crashes every 2-5 minutes. They seem to be random, but changing the player's position using their playerdata fixes it temporarily until the next person causes it. I've attached a

[media]

.

Ahmet Atakan KESKIN
[media]

   I am having the same issue for 1.13,1.13.1.This seemed to happen to me after a electric cut.

Adam P

Same or similar issue in 1.13. Newly installed server.

[media][media][media][media]
Josh Fitzpatrick

Having same issue 

[media]
Adam P

Same issue on server 1.13.1 when trying to reuse the same world files in previous post. No problem however with new world files with a reinstall. Apologies if this description is not technical and specific (I don't play the game but host a server for my kids). Problem was described to me as "I walk too far from the spawn which causes the crash." After a server reboot, ""when I log back in it tries to spawn in the same place but it doesn't load the land again." Ultimately someone else in the game will cause the server to crash again for the same reason. 

John Spanos

The world in the link contains a region (r.1.4.mca) that will crash the world. Use the following steps to reproduce and to resolve the crash.  Note, you will lose data by deleting chunks, but at least your world will no longer crash.

CrashWorld

Start the world
Teleport to 679 100 2118 (chunk 42, 132) - Can use command block to tp.
Game will crash

To fix, use an NBT editor like NBTExplorer and delete the 9 chunks surrounding chunk 42,132
41, 131
41, 132
41, 133

42, 131
42, 132 * (problem chunk)
42, 133

43, 131
43, 132
43, 133

Start the world again and the chunks will be re-created and no crash.

Just deleting the problem chunk does not resolve the problem.

This world was created in 1.13.1, but the region file r.1.4.mca was converted from 1.12.2

Asteraoth

Can confirm with the world that @unknown provided.

Jason M

I had looked for a while for a way to delete corrupt chunks. I'm not a computer programmer, but within an hour I watched a short online video by PythonMC, downloaded NBTExplorer, and deleted the corrupt chunks from my world. Thank you John Spanos and others!

hans riesebos

Had the same crash. Everytime a coordinate was approached, the server crashed with this exception.

Deleting the chunk and the 8 around it did not solve the problem. Our world is operating now after these steps:

1) Delete the chunk and the 8 around it.

2) Load the world in singleplayer

3) Go to the chunk. In our case the chunk got generated, but it does not fit nicely in its surroundings.

4) Copy the world back to the server and all is well again.

Asteraoth

Does anyone still have this issue when using 18w45a?

Franco Nicolás Agüero

I have the same problem. How to know what file i have to delete?

Alex

I am still getting this exact, same issue on snapshot 18w47b.

 

[media]

 

http://www.mediafire.com/file/vlt4y9ttc5zulfx/CORRUPTED+WORLD.zip

 

Coordinates are around -2976 ~ -4736

 

Issue is experienced in single player.

 

 

Pamela F

Same issue occurred today in 1.13.2 server. Tried doing what hans riesebos did on 08/Oct/18. Did not work for me as it crashed in single player as well. Tried replacing the entire offending .mca file with an older backup. Crash still occurred. Had to use a backup for the entire world.

http://www.mediafire.com/file/5eulax7tt0fnjlo/corruptedworld.zip

approx coords causing crash 2014, 527

[media]

 

 

 

Rafael M

Hello, I'm having the same problems in my 1.13.2 server. It happened during the night while I was not online so I'm not sure about the circumstances.

[media][media][media][media]
Fly

Yup. This is still very much an issue.

[media]
Daniel Sedeño

This happened to me too while traveling on the Nether, I play on versión 1.13.2, and when I try to rejoin my singleplayer world the games crashes again. Can someone tell me how to fix it? Or it can't be fix on the moment?

Teemo Cell

Got the same problem. Server crashed while i was not home.

Ethan

ok, so this started happening with my single player survival world, I have a optifine, shaders and a texture pack on this world, however it starts to load into the world and gets to 60% then the game crashes, I do not know why this is happening, all i know is that I was doing a bit of exploring when it happened

Ahmil Jilani

Happens to me reliably on a 1.13.2 singleplayer world that's just about a minute old. Steps to reproduce:

  1. Start up the world

[media]
  1. Wait for about five seconds.

  2. Crash! Log:

[media]

I've attached the world and the log.

HazMattMC

I would submit my blog post on the matter:
“Exception generating new chunk” – A Detailed Fix Method

http://koastal.world/exception-generating-new-chunk-a-detailed-fix-method/

erik tuttle

So how is the problem fixed then?

Kai Cook

Same issue on 1.13.2

Adrian Östergård

Is this still an issue in 19w11b?

Asteraoth

Cannot reproduce with @unknown's world. However, I can still reproduce with @unknown's world.

[media]

Edit: It appears that their world is modded.

Joshua Pynn

This is still an issue, I myself just ran into it. Only difference is that I wasn’t on a multiplayer server, it was just my own solo world. Anyone know a temporary fix?

[Mod] Neko

@unknown: @unknown posted a workaround that involves deleting the affected region file (which I don't recommend, you can lose a lot of data).

Can you attach (or provide a download link of) the world here?

Joshua Pynn

Hey Neko,

Do you just need the seed? I don't know what to post if you want the exact world. Kinda new to this. I've attached one of the crash reports to the post however. 

[Mod] Neko

Providing the seed wouldn't work because it's a problem with how the game saved.

In order to attach the world, locate your world saves folder (.minecraft/saves), make a copy of your world, zip it, and attach it here (see the "Attach Files" button at the top of this ticket). If the world save is too big, please upload it to a file sharing site and comment the link.

Joshua Pynn

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

[Mod] Neko

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?

Joshua Pynn

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

[Mod] Neko

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.

Joshua Pynn

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