Minecraft crashes randomly while playing remotely one someone else's world. After this, attempts to rejoin the world fail with either "unable to join world" or minecraft crashing with high memory usage. This is specific for the gamertag/microsoft account, and occurs when attempting to join from other devices with the same gamertag/microsoft account. It also occurs when attempting to join from an Android device, though it will just show a blue pale screen. It is also world-specific, as it doesn't occur with different worlds.
Opening the world in rbedrock (R library for world analysis), the remote_player key contains a the value "Rotation" which has NaN for the first value, and -90 for second value.
If these are both set to '0', the player can rejoin the world without problems.
I've attached the values from rbedrock that seem to be the cause of the crash - you can see one player has NaN for the first value of Rotation, but not the other. This is associated with the player who is unable to join.
Linked issues
is duplicated by 2
relates to 1
Attachments
Comments 15
I suspect MC-201406 is a duplicate although in that case they edited the world data with a remote 3rd party tool. In my case the data was caused by gameplay in the client and I could only restore access by using a 3rd party tool to fix the corrupted data.
Looks like this issue can be fixed without 3rd party tools. In my case (world was at Bedrock Dedicated Server) it's fixed by teleporting bugged player to other player(or to himself)
@Randi: how do you teleport a player if they can't log in? AFAICT you can only act on players who have logged in.
I think if you join the world from an android device, rather than just crashing, it seems to show a blank blueish screen. You can then fix it by teleporting, which I guess is the equivalent of editing the player position in rbedrock.
I'm still trying to check where that does happen, but it seens to be always related when the camera tilts due suffocating by something (lava, water, gravel, sand etc...)
I also can confirm that still affects 1.18
@Magdalena Wardak I couldnt reproduce the same issue on 1.18.2 with the same scenario. So looks good to me 😃
I've been playing around with the recent 1.18.2.03 build and doing a lot of underwater digging and so far nothing has tripped up. @Magdalena was there an explicit fix added to the build for this.
I can confirm I've seen this bug. Whatever the mechanism that leads to the corruption of the remote data held on the server the player will not be able to join from any BedRock edition client thereafter (tested with Android x86/arm64 and PS4 clients). Generally the screen may start up with item bar and a blank void before eventually crashing the client. The only way to restore login is to manually edit the world data to a sane rotation value.
I suspect the best way to approach this is to defensively handle NaN values when first loading the player location and restoring a sane default when it's broken.