A chunk is failing to load, causing immediate crash with asserts ON, but occasionally causing crashes with asserts OFF especially in multiplayer.

A chunk within a ticking area is failing to load, crashing the game when the world is loaded while asserts are ON. Occasionally, the game crashes with asserts OFF when trying to save & quit, or teleporting far away. The same error is crashing the game in multiplayer for players joining the game, where, if not on world load, their game will always crash shortly after due to the unloaded chunk. The chunk in question is the ticking area “master” where command blocks are kept that run the map; The error does not occur if the ticking area is removed, and the chunk loads as intended, but the ticking area is necessary for the commands to run.

Impact:

This error is preventing content from being released, as even having asserts off causes crashes in single and multiplayer.

 

You'll need to download MLv0.6.1 that I've posted in the Everbloom Slack because it's slightly too big to attach. I can't recreate the bug consistently in any other world.

Repro Steps:

Singleplayer or multiplayer with asserts on: 

1. Load our world with asserts on

Singleplayer with asserts off:

1. Load our world with asserts off
2. Save and quit the world repeatedly until crash

Multiplayer with asserts off:

1. Load our world with asserts off
2. Save and quit the world repeatedly until crash

1. Have second player join 
2. Map will crash for second player after a few moments

 

Note:
Player 1’s game will occasionally crash when saving & quitting in multiplayer just like in single player.

 

Observed Results:

Game crashes because the chunk wasn’t loaded, indefinitely with asserts ON, and occasionally with asserts OFF.

 

Expected Results:

Game to not crash, and for the chunk to load, regardless of asserts being ON or OFF.

 

Regression Builds:

Unknown

 

Notes: 

This is the error: 

[ERROR SYSTEM 6952 17612] Assertion failed: Something went wrong, the chunk wasn't loaded

Condition is false: false

Function: LevelChunk::setupRedstoneCircuit in f:\darwinwork\395\s\handheld\src\common\world\level\chunk\levelchunk.cpp @ 2196

 

I’ve tried moving the commands to a new area and creating a ticking area with a different name, but the error persists. I’ve tried making the ticking area a different size, but the error persists, even if the ticking area doesn’t have any redstone related blocks.

 

It’s also noteworthy that there is another ticking area in this world, “display”, that is NOT giving this error, and doesn’t crash the game even with asserts ON.

 

The ticking area “master” for the command blocks is located at 0, 0, 0