[MCPE-19354] Unexplored area on map causes realm to crash Created: 21/Dec/16  Updated: 26/Apr/17  Resolved: 16/Mar/17

Status: Resolved
Project: Minecraft (Bedrock codebase)
Component/s: None
Affects Version/s: 1.0.0
Fix Version/s: 1.0.4.11

Type: Bug
Reporter: Joseph Atkin
Resolution: Fixed Votes: 15
Labels: crash, map, realm, unexplored

Attachments: PNG File Minecraft_ Windows 10 Edition 1_16_2017 8_13_21 PM.png     JPEG File ProblemSpots.jpg    
Issue Links:
Duplicate
is duplicated by MCPE-19701 create Maps Resolved
is duplicated by REALMS-251 Maps Resolved
is duplicated by REALMS-267 Loading map at 4x scale sometimes cau... Resolved
is duplicated by REALMS-275 Exploring with a map causes Server cr... Resolved
Confirmation Status: Confirmed
Platform: Windows
CHK:
ADO: 54098

 Description   

While exploring with a map selected in the hotbar causes the realm to crash in certain areas. All players on the server are also kicked, and no one is able to rejoin the server for about 5 minutes with error "Unable to connect to world". When traveling to area without a map, everything works fine.

*UPDATE* This issue only occurs when a) you venture into the area in which it is occuring; AND b) the map is selected in the hotbar. If you select the map while within the area of the problem, the server will crash. Again, the entire realm crashes; I know this because it kicks all players off, not just the person with the map. I have recreated this problem with two different computers on two different LAN's, and two different realms (one is survival and the other is creative), with the other players either on the same LAN or on seperate LAN's. It is easiest to recreate this issue on creative mode (because of flying), with a 1:16 map (I have had it on both 1:16 and 1:4). I have not been able to figure out why these areas cause a crash. I can go through both areas without a map just fine. Neither one is the same biome (one is a hilly beach area and the other is a swamp).

Seed:
-635438843

Coordinates:
588, 109, -1633
309, 79, -372



 Comments   
Comment by Joseph Atkin [ 16/Mar/17 ]

I no longer have this issue in the updated version. The maps don't crash the game.

Comment by [Mojang] Adrian Östergård [ 16/Mar/17 ]

Please reply and update affected versions if you're still able to reproduce this issue in either 1.0.4.11 or 1.0.5.3.

Comment by erin webb [ 20/Jan/17 ]

My realm appears to have the same issue....creating maps in 1:2 certain ones cause the realm to crash and kick everyone out. I seem to notice this issue in high mountain area.

Comment by SPENCER DREDGE [ 20/Jan/17 ]

What kind of information will help with this issue? Do you need more testing or more information to find the exact cause of the issue?

From my experience I am simply unable to create the blank map, or hold it actively in my hands without this happening. I get a few seconds of blank map with a marker for myself when I have done this on accident. I havent' found more than one area that does this and I am still unsure as to how large the area is but I assume it is a single unzoomed map size that is to blame.

Anybody care to specify the biome/biomes they had the issue with?

Mine was the dark forest/mushroom/lush forest biome. Like a Dark oak forest with big mushrooms. It might be on the border of another biome also. If not it is right next to another biome. The area had some exploration and minor building but nothing extensive. no buildings just random blocks placed, torches, chests, misc dirt, stone plants, etc.

A the common blocks are in play all over with no issues.

My thought is if there is a commonality that is not extremely technical, it has to do with the biome? Or maybe the border of 2+ biomes. More were very close it could have been like a biome edge nexus or something! Maybe up to 4 biomes were nearby (in sight).

So anybody else know if biome borders may have been involved in your crash area or anything like that?

Comment by Joseph Atkin [ 19/Jan/17 ]

My appologies. You are right. What I meant is that it is nowhere near as complete as the Java version. Once it is, it will be better than the Java version (because Java is a horrible way to create a game on the scale as Minecraft). I too wish that these bugs will be fixed with expediency. Getting angry won't help; giving good and accurate information will.

Comment by Trustin Johnson [ 19/Jan/17 ]

With the utmost respect, this game is now out of beta as V1.0.0 and the Realms service costs real money. These types of game breaking bugs on a released/shipped product should be considered unacceptable and highest priority, as it is a sure fire way to quickly lose customers and damage reputation. I do trust this bug (and breaking bugs like it) are being investigated properly internally, but with regard to general discussion here and abroad, I believe that the game is at the point where blaming or pointing out beta status should no longer be an acceptable explanation for why a frustrating game breaking bug exists.

Comment by Joseph Atkin [ 19/Jan/17 ]

@Nikki, yeah it's a beta game so it is bound to have some bugs. Sorry to hear about your bad experiences.

If you were the owner of the realm you can find the coordinates following instructions on an earlier comment I made. If you need, I will repeat the instructions. If your husband is the owner of the realm he will have to do it (unless he is still stuck not being able to log in). The more information Mojang has from us, the better, but don't fret it too much.

Comment by K. Nikki Buckingham [ 18/Jan/17 ]

Well our Realm is all ready trash. My husband works far away and the Realm is how my daughter, sons, and I "hang out" with him, and two months ago he experienced the "Blaze death crash in the Nether" and has not been able to log in since. This is just the icing of a festering rotten garbage cake. I got to my jungle finally and used a compass to block-road back to base. I've been following the road and mapping it out. I map it all then zoom out and map it all then zoom out and map it all (so my maps are at 2:4 in the end). I do 2-3 maps and then go back to my jungle and hang them on the wall. Everything went great for the first 8 maps so I guess I was lucky....On map 9 as I got near base (map 10 will be base) I encountered one of these broken chunks on the last corner. I tried a few things...Like, I put the map away and walked around hunting and collecting bamboo on that section...it all did fine...but when I pulled the map out the pointer froze and the realm crashed....You may remember me from such bugs as...."Crashing while mapping" and "item frames crash realms" and "maps disappearing from chests"....I'm our cartographer, and I've waited many many months to be able to map properly. Kept having to give it up when each update gave me new problems.

I'd send more info (like coordinates and seed) but I"m a little tubby housewife gaming nOOb. I just want to play my game. I suspect you guys probably have enough info to be working on this all ready, but if you need more..... sigh...someone would have to walk me through it step by step how to get the Realm off the Realm and how to get the coordinates.

Windows 10, v 1.0.0 on desktop PC

Comment by Cecil McIntosh [ 17/Jan/17 ]

Yup this thing is real. My realm totally depends on being able to map the know World people!!! The game is unplayable like this! Please prioritize

Comment by Greg Daly [ 17/Jan/17 ]

Here is a sample of a map before a realm goes down. The chunk(s?) you're in will not render on the map, and you know a server crash is imminent.

Comment by Ryan Radia [ 17/Jan/17 ]

This is also a serious problem in our realm. I too have lost several horses/saddles due to this bug. Escaping the issue entails running out of the affected area while removing the map of the area from the hotbar. It's extremely frustrating.

Comment by Greg Daly [ 17/Jan/17 ]

I've seen this many, many times on our realm. This should be a top priority as it's affecting playability. BTW, Mojang should already have the logs from all the server crashes.

I lost a horse and a saddle once from this bug, btw, so I'm not surprising that you lost a boat. Anything that you're in or riding is subject to disappear.

Comment by Joseph Atkin [ 14/Jan/17 ]

@Jonas Go into edit for your realm (the button that looks like a pencil). Click "Download world". After it downloads it will show up in your local worlds list (usually called "(your realm name) - copy"). Edit that world and enable cheats, then go to the area causing the problem, bring up the cheat menu by pressing / and type tp ~ ~ ~ (so it looks like "/tp ~ ~ ~"). This will give the coordinates and ensure you don't enable cheats on your multiplayer realm.

Comment by Tourniquet [ 14/Jan/17 ]

We have similar problems. It's pretty upsetting.

1) In our first world we couldn't look at the map at all, it would stay empty and a couple of seconds later the realm crashed.

2) Because we thought the World was corrupted we started fresh, this time around the realm crashes very often if you explore new area.

And now we have another problem. The boat we were on is gone and if we reach the island we found it crashes all the time. We can't do anything anymore. Please fix it

We can't look at the Coordinates because we disabled cheats.

Comment by Joseph Atkin [ 14/Jan/17 ]

Ok, I was able to find the seed and coordinates. For anyone interested, you have to download your realm locally to get the seed. Enable cheats and go to the problem area. Press the / key and type "tp ~ ~ ~" (without the quotes). This will give you the coordinates.

Seed:
-635438843

Coordinates:
588, 109, -1633
309, 79, -372

In order to replicate the bug, it has to be on multiplayer realms. The first coordinates will put you on a mountain with spruce trees, if you create a map right there the server will crash.

Comment by Rachel Jones [ 13/Jan/17 ]

I also have this issue in windows 10 realms. seed 690589143. I can't get coordinates but if I make a map at spawn and zoom it all the way out, when I go just north of that map to make another map is when it happens. It happened in a couple different areas not far north of the first map.

Using a blank map caused it to generate a blank map for a second, then the realm crashed. When I came back, the map was no longer in my inventory.

Comment by Joseph Atkin [ 12/Jan/17 ]

It's Windows 10 beta version. Seed shows as 0 and there is no way to find coordinates. Also, it happens on every seed but only while on a realm. If the world is downloaded locally, it does not crash.

Comment by [Mojang] Adrian Östergård [ 12/Jan/17 ]

Please add which coordinates and what seed you're using where this happens.

Comment by Joseph Atkin [ 08/Jan/17 ]

I have tried a couple of things. Firstly, I went to the problem areas and attempted to use an empty map to see if it would do anything. It renders a blank map and then crashes the game. So I downloaded the world to my local computer and tried it from there. When downloaded and played locally, the maps do render without the game crashing. However, while in the problem areas, my CPU usage jumps from around 10% to 70% and the terrain takes about 25 seconds to fully load. My CPU remains running high while in the problem area but drops back to normal when outside of it. What I've noticed is it mostly happens when there are 3 or more biomes within an area. On the attached image you'll notice that the upper right problem area is the intersection for a swamp, forest, and plains. The bottom left is a little harder to tell, but it is an ocean, plain, and forest. However, there are other areas that have 3 biomes with no issue. I have tried looking all around the problem areas and have not noticed a discernible pattern. As Dino Roger mentioned, his problem happens around villages and indeed, both problem areas on my screenshot have villages close by. But there are several other areas with villages that I've explored with no issue at all.

Comment by Dino Roger [ 02/Jan/17 ]

Had the exact same problem. If map is in the hotbar even not selected game would crash. Happened multiple places mainly near towns. My map was level 4 but have not tried with lower levels maps.

Comment by Joseph Atkin [ 21/Dec/16 ]

These are the areas in which the problem is occuring

Generated at Sat Jan 11 15:22:53 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.