Server crashes while generating new chunks – java.util.concurrent.ExecutionException: We are asking a region for a chunk out of bound

See MC-129253, it was reproducable in 18w19a with seed: 8223045022386406090, however, in 18w19b this seed does not crash me anymore (tested 3 times).

Uploaded my 18w19a crash log as well as the screenshots of the complete game output, from a 18w19a crash with said seed.

Confirmed in snapshot 18w19b. Crash happens at spwan with seed: 8223045022386406090
Tested this seed 3 times. Attached

OS: Linux ver 4.13.0-41-generic #46~16.04.1-Ubuntu SMP Thu May 3 10:06:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
Java: ver "1.8.0_171" (Oracle)
Launcher: Minecraft Launcher 1.6.89-j (through bootstrap 5)

This appears to be bringing down my 18w19b server continuously...
–

---- Minecraft Crash Report ----
// I bet Cylons wouldn't have this problem.

Time: 5/9/18 10:59 PM
Description: Exception generating new chunk

java.util.concurrent.ExecutionException: java.lang.RuntimeException: We are asking a region for a chunk out of bound | 3758 -20
	at java.util.concurrent.CompletableFuture.reportGet(Unknown Source)
	at java.util.concurrent.CompletableFuture.get(Unknown Source)
	at si.c(SourceFile:130)
	at sq.a(SourceFile:84)
	at sr.c(SourceFile:143)
	at sj.i_(SourceFile:223)
	at net.minecraft.server.MinecraftServer.w(SourceFile:689)
	at ru.w(SourceFile:364)
	at net.minecraft.server.MinecraftServer.v(SourceFile:622)
	at net.minecraft.server.MinecraftServer.run(SourceFile:527)
	at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.RuntimeException: We are asking a region for a chunk out of bound | 3758 -20
	at so.c(SourceFile:115)
	at bay.y(SourceFile:45)
	at so.a_(SourceFile:121)
	at bto.a(SourceFile:144)
	at bto.a(SourceFile:16)
	at bxn.a(SourceFile:20)
	at bxn.a(SourceFile:13)
	at brp.a(SourceFile:27)
	at bbr.a(SourceFile:516)
	at bpc.a(SourceFile:109)
	at sx.a(SourceFile:12)
	at sw.a(SourceFile:33)
	at bpg.a(SourceFile:85)
	at tc.a(SourceFile:59)
	at tc.a(SourceFile:23)
	at afz$a.a(SourceFile:143)
	at java.util.concurrent.CompletableFuture.uniApply(Unknown Source)
	at java.util.concurrent.CompletableFuture$UniApply.tryFire(Unknown Source)
	at java.util.concurrent.CompletableFuture$Completion.exec(Unknown Source)
	at java.util.concurrent.ForkJoinTask.doExec(Unknown Source)
	at java.util.concurrent.ForkJoinPool$WorkQueue.runTask(Unknown Source)
	at java.util.concurrent.ForkJoinPool.runWorker(Unknown Source)
	at java.util.concurrent.ForkJoinWorkerThread.run(Unknown Source)


A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------

-- Head --
Thread: Server thread
Stacktrace:
	at java.util.concurrent.CompletableFuture.reportGet(Unknown Source)

-- Chunk to be generated --
Details:
	Location: 1877,-8
	Position hash: -34359736491
	Generator: bqx@497d0c75
Stacktrace:
	at si.a(SourceFile:180)
	at si.c(SourceFile:133)
	at sq.a(SourceFile:84)
	at sr.c(SourceFile:143)
	at sj.i_(SourceFile:223)
	at net.minecraft.server.MinecraftServer.w(SourceFile:689)
	at ru.w(SourceFile:364)
	at net.minecraft.server.MinecraftServer.v(SourceFile:622)
	at net.minecraft.server.MinecraftServer.run(SourceFile:527)
	at java.lang.Thread.run(Unknown Source)

-- Affected level --
Details:
	Level name: world
	All players: 1 total; [sl['CoolReign'/310, l='world', x=30008.48, y=47.87, z=8.13]]
	Chunk stats: ServerChunkCache: 497 Drop: 0
	Level seed: 1505535
	Level generator: ID 00 - default, ver 1. Features enabled: true
	Level generator options: {}
	Level spawn location: World: (193,64,-8), Chunk: (at 1,4,8 in 12,-1; contains blocks 192,0,-16 to 207,255,-1), Region: (0,-1; contains chunks 0,-32 to 31,-1, blocks 0,0,-512 to 511,255,-1)
	Level time: 821556 game time, 843535 day time
	Level dimension: 0
	Level storage version: 0x04ABD - Anvil
	Level weather: Rain time: 14377 (now: true), thunder time: 13910 (now: false)
	Level game mode: Game mode: survival (ID 0). Hardcore: false. Cheats: false

-- System Details --
Details:
	Minecraft Version: 18w19b
	Operating System: Windows 7 (amd64) version 6.1
	Java Version: 1.8.0_171, Oracle Corporation
	Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
	Memory: 365195928 bytes (348 MB) / 1057488896 bytes (1008 MB) up to 2854223872 bytes (2722 MB)
	JVM Flags: 0 total; 
	Profiler Position: N/A (disabled)
	Player Count: 1 / 100; [sl['CoolReign'/310, l='world', x=30008.48, y=47.87, z=8.13]]
	Data Packs: vanilla, file/veritas0923 (incompatible)
	Is Modded: Unknown (can't tell)
	Type: Dedicated Server (map_server.txt)

I got this tonight on a world with the name and seed of 18w19b. I was teleporting around looking for a reef, /teleport @p 1000 100 1000, then 2000 100 2000, etc. When I got to 6000, 100, 6000, the server just crashed. Restarting it and logging in again resulted in another server crash, on and on.

I uploaded my crash log also. I will note that the server was generating chunks hard since I was teleporting around, but it's a fairly powerful PC (with SSD) so I'm not sure how hard it was actually struggling or if that had anything to do with the error.

Someone had attached a crash report:

with the seed: -7269461605076408993
Using this seed the world never loads for me, sitting at "Loading world" with no progress or cpu usage. I have to kill the process. A crash report is created.

Affect me in 18w19b, wanted to test new features, but I quickly encountered this bug.
First time it triggered right after I picked elytra from the creative menu and tried to fly. I am unable to return to that world.
So I made a second world with a different seed, everything seemed fine, but when i wanted to teleport to 1000, 100, 1000 it happened again, making me unable to return to both worlds.

1st world:

2nd world:

Similar issue. Not sure if helpful but I also included a screenshot of the chunk from 18w16a. It's the edge of an ice spike biome.

I attempted to report a similar issue (MC-129520) but the bot "resolved" it then told me I was using a pirated copy of Minecraft?  I own two licenses from minecraft.net!

Crashed today using 18w20a - See attached crash log.

Description: Exception generating new chunk

java.util.concurrent.ExecutionException: java.lang.IllegalArgumentException: bound must be positive

This bug is making it difficult to even evaluate the snapshots. I currently am experiencing ~30% of new random seed worlds crashing with this exception. Sometimes near to spawn, others about 5 to 10 minutes into the game both survival and creative. I propose bumping up the priority on this if at all possible, to allow us to test an review new features and fixes. Respectfully, until then it's somewhat a waste of time to load a snapshot.

Experiencing the crash in almost every newly generated world. Sometimes the problematic chunks are near the spawn, so it's impossible to load the world.

Tested couple worlds, two are stuck in an infinite loop crash:

-6094121500719519903 <World is too big, 37 MB> 

-5498276653864705625 

This Bug is a big problem. Testing or even playing is nearly impossible. So i think its a high prio bug.

Wanted to add my upvote here as well. My players and I have also determined exact coords inside our world running on 18w20b that cause the crash listed above. We're running on Ubuntu 16.04, multiplayer survival, on Oracle Java 1.8.0_171. World was originally generated on 18w19b with a world seed of k1w5sWlDeWjSoVrHPUpQ - crash however is happening on 18w20b. Coords to reproduce the crash: x: -2896.976, y: 62.073, z: -7229.122

If this is a world generation problem, meaning you need my exact version of the world, let me know (mention me here) and I can upload. It's rather larger at this point however which is why I'm, refraining from just posting it. I guess we were lucky in that respect to not hit it early on? 

Confirming this for 18w22b. Crashes seconds after loading. Totally unable to test 1.12.2 world.

Don't see my duplicated comments here but game crashes when I explore in one particular direction although the chunk where the game crashes varies. I have numerous bug reports if they are any use. This occurs on 18w22b and the previous snapshot as well. As I was playing in snapshots I am unable to utilise any of the usual methods of fixing my world.

@unknown Can you give me the seed and location where you get the crash ?

@unknown Can you confirm your 18w20a Test 2 world still crash in 18w22b ? I just tested it and it works fine for me.

@@unknown My seed is  -6968998364217797098.

The locations are as follows...

chunk 55, 71 (multiple times) and chunk 57, 71 (once).

Hope that is useful.

@unknown The world '18w20a Test 2' loads fine in 18w22b for me too. Will test other worlds and report the results later when possible.

In 18w22c I no longer experience a game crash when I (re)test these commented on seeds:

8223045022386406090    commented on by @unknown and @unknown
-7269461605076408993   commented on by @unknown
-6968998364217797098 commented on by @unknown at/near chunk 55,71

The 3rd on the list, I approached said chunk from 4 directions each in different tests. I also launched the game with default JVM arguments, and using -Xmx3G (memory bug: MC-121318).

Can anyone else confirm a fix here ?

Minecraft had been crashing with this error on one of my worlds in two locations, but a while back it stopped happening.

I ran another test this morning. A couple of things. First When I head in the direction of 55,71 I experience a lot of jerky gameplay almost like my powerful laptop is struggling but the debug screen reveals that barely 13% memory is being used, this has happened every time I've encountered this problem. Secondly, although the bug report I got this morning mentions a problem with 55,71 I was nowhere near that point when the game crashed. I can't remember exactly where I was but it was something like 36,65.

After quite a few tests I didn't encountered any crashes, caused by errors during chunk generation / loading.
But sometimes a brand new world (initial) generation during the loading screen is way slower than normal.

Also tried converting worlds, generated and saved in 1.12.2 to 18w22c.
There were no crashes again, but the alredy generated chunks in 1.12.2 were loading (converting) very slowly in 18w22c and a strange grid-like pattern of alternating biome variants was generated in oceans (which doesn't occurr in newly-generated 18w22a/b/c worlds), but that could be a different bug.

World generated in 1.12.2

Converted to 18w22c

Screenshot in 18w22c

@unknown I have experienced that same game stutter near chunk 55,71 only when using the default JVM arguments.
You had commented crashing "chunk 55, 71 (multiple times) and chunk 57, 71 (once)".
In your latest comment you were nowhere near that point when it crashed. I have retested both of these areas and have not experienced any issue.
Perhaps it would be helpful if you provide that crash report and/or retest that seed/areas and report back providing that crash report. There is a frozen ocean next to 3,55. Some of the crashes I've experienced in the past happened near this biome type.

@Xavom

As I said the report says that the game crashed whilst generating 55, 71 but although I was heading in that direction I wasn't near to that chunk.

@unknown I tried several more times using the info in your crash report. The crash location was about 651, 64, 1054. I even tried your JVM arguments. The only time I experienced anything (100% memory stops/starts) was when I created the world in 1.12.2 first, then loaded in 18w22c using default JVM's . But still no crash.
Could the issue here be that your world was generated in a previous snapshot?
Have or can you generate from 18w22c and head to the crash site?

I ran the experiment.Started new world using my seed. Made my  to the crash point - 55, 71. The game still definitely became more laggy but there was no crash.

I started my original world in a snapshot but I can't remember which one but it wasn't the latest one or perhaps even the one or two before that.

So all in all, this issue can be considered as fixed.

No. It may not be reproducible in this particular case, but I just cannot walk around in my world without it happening within 3 minutes. Also, when it occurs, some existing chunks may get wiped out, regenerating as new chunks when visited.

@unknown Was the world file you experience this in generated in a previous snapshot? If so could please generate again using the same seed in18w22c and try to reproduce it?
I am currently testing all of the seeds from the attached crash reports that refer to "We are asking a region for a chunk out of bound".

18w22c:
I have tested the seeds from the attached crash reports having runtime exception "We are asking a region for a chunk out of bound". For each seed, in creative, I flew towards the player location in the report. Then canvased an area of roughly 12 x 12 chunks centered on that crash site. In each case I did not experience and issues.

Xavom, it's a 3 year old world, currently running perfectly fine in 1.12.2. I was a bit mistaken about the error though. Although I've seen "We are asking a region for a chunk out of bound" a few times, it's not often. The errors I get the most are "Couldn't load chunk" and "Couldn't load protochunk". They're extremely frequent. I haven't been able to run that world for more than 3 minutes since 18w22a.

Everything runs fine when I create a brand new world in 18w22c, using the same seed. I can't recreate the issue.

I can't find any report about those two errors. It may or may not be related to this issue.

@unknown, please create tickets about the two errors. Attach the crash report / launcher_log. Leave there a reference to this ticket.

@Kumasasa

It won't be necessary. It seems I was testing in 22b, thinking it was 22c (the launcher said 22c for some reason). These errors don't occur in 22c. I get huge lag spikes instead of crashes and ~6-10 TPS instead of 20. 

Sorry for the mistake!

Ok, no problem.

Tested again this morning. I still experience exactly the same lagging and crashes with 22c as I did with previous snapshots.

What I'd really like to know is, is there anything I can do about it? Will the full 1.13 update fix this? is my world just corrupted beyond repair? I'm not really clear on where I go from here. Is this problem that I'm having being worked on?

Thanks for any help you guys can give.

I don't get crashes with 18w22c. But the lag spikes and tps drops are unbearable. Chunk loading speed is also excruciating slow, at roughly 2 seconds per chunk. This is all in single player.

I've decided to test my world on a server, since it's already a server world. Things got dirty, fast. A server cannot run my 1.12.2 world at all. Errors spam the console (like 1 full page per tick) as soon as I try to log on. After a few seconds, the server just crashes. Nothing that can be done. Impossible to log onto it.

Also, if I convert my 1.12.2 world to 18w22c in single player beforehand, it will run on the server afterward. As if the server cannot convert the world properly. But still, the server will lag very badly, with TPS not exceeding 8-10 (1st night lasted ~25 minutes), and numerous "Can't keep up" messages hammering the console repeatedly.

@unknown, this is a bunch of new issues. Please create the appropriate tickets with the server log(s) attached.

@unknown I'm experiencing the exact same issues, along with many others. I have created MC-118106 a long time ago and recently updated it.

@Kumasasa

I don't get the error spamming in 1.13-pre1, but I do still get the "Can't keep up" messages. The problem remains exactly the same though. I'll wait for some feedback from Grum before creating a new ticket, as he will be investigating the problems using my world. I may be an isolated case or there could be a problem with the world itself. 

@VideoklipBG

I don't know. That issue dates back to 1.12. The issue I'm having is brand new (since 18w20a). I've never encountered it before. This world runs perfectly fluid on a 1.12.2 smp server. 

@unknown Well, 1.12 runs faster than most the recent snapshots, especially. But I'm also experiencing the insanely slow 1.12 world loading / conversion to 18w snapshots, including 1.13-pre1 currently.

@unknown Since this bug with this error is resolved, I suggest maybe to contribute your information to the ticket suggested by @unknown, MC-118106 the description there is very close to yours. Although as @unknown said this could a be new issue. I would search and create a new ticket if needed. The previous error (crash report) and the new issue you're experiencing are not the same per title as this bug here.
As soon as I free up today, I'll try to recreate what you're experiencing.

@VideoklipBG

I agree. The conversion process really needs good optimization. In its current state, it can be a huge problem for populous vanilla servers.

@Xavom

OK I will do that. Although that report is "old" and my problems only happen in 1.13, it describes the problems quite precisely. 

Still happens in 1.13-pre10, while I was exploring near the world border, and game crash. 

Can confirm affecting 1.13-pre10. Using same seed as @unknown comment.

EDIT: Also, cannot reload the world without it crashing. I was however, after a few attempts, able to pop of this screen shot.

Confirmed for 1.13 release

Confirming this still occurs in the 1.13 release. I've been able to consistently trigger the bug by teleporting to coordinates at 10,000,000+ and moving around for a few minutes. Going to 12 million and higher it often crashes within seconds. Coordinates closer in sometimes also caused the crash but not as often. Attempting to enter the world again causes another crash. Tried this across several different worlds with random seeds, all newly created in 1.13.

Same problem with different worlds create in release 1.13 😞

Crash caused by teleporting to big coordinates is MC-133839 and should be fixed (after the next release), everything else should've been fixed earlier.

I am still getting crashes for this reason

@unknown, does MC-131071 describe your issue?

I'm just got this error is 18w30b. I can't load the world it just crashes in a second or so.

Please attach the crash report.

Not fixed, why is it listed as "resolved"?
I got a crash that caused a BSOD and the error report is linked.

It is listed as "resolved" since the issue has been fixed (see fix versions).

@unknown, you got that crash on the still affected 1.13, but this issue was fixed for 18w30a.

Which is why I made a new one but someone closed it saying it's a duplicate.

Is my hardcore world lost forever?

If you haven't understood already, this bug has been fixed for the next release.

Ohh, makes sense now. Thank you.
Sorry to all I may have offended, I tend to take things extremely literally and when there's no information I assume the worst.
Survival habits that work irl, don't work so well virtually.

i have a the same error message on my 1.13.1 server when i go to the nether, the server crash. And now, when go back to the server, it crash again and again with the same error message.

the crash report :