Worlds corrupt with no valid reason: std::length_error (Exit code 6)

[Polytelus]

After some gameplay time, worlds become non-accessible. Reverting to previous versions is forbidden, so that cannot be tested. Hardware and last log of the world is available in the pastebin below. Both worlds give a std length error, and an exit code 6 as per the pinned issue. I really want to play in these again, but I don't like the idea of having to pull out my phone to do so. Playing bedrock on mobile is awful.

OS: Arch GNU/Linux, fully updated with pacman.
Hardware type: Laptop, Mobile Processor / Samsung Electronics NP370E4J-BW2BR
CPU: x86_64, Intel Pentium Slivermont/Baytrail N3540 - Running on MESA (Latest) (No discrete GPU)
Launcher Version: v0.2.3 (build 28)
Game version: Minecraft 1.17.10.04 (X86_64)

World logs:
https://pastebin.com/5M7ceY8c
https://pastebin.com/2zxifxgs

[Polytelus]

Similar to: #560

[g0jus]

Could you provide crashing world for investigation? Thanks

[LrrrAc]

Im having the same issue on a server. Played fine for hours, spent too long in water and client crashed. Rejoining caused both client and server to crash as specified above. Unable to TP char as the server crashes on login. My zip is too large to post. How can I share?

client:
OS: Ubuntu 21.04
CPU: 3600k
GPU: GTX 1070 FE
Launcher Version: v0.2.3 (build 28)
Game Version: 1.17.11.01

Server:
OS: Ubuntu 20.04
CPU: 2600k
Version 1.17.11.01
Docker Container: https://hub.docker.com/r/itzg/minecraft-bedrock-server