You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I'm sometimes getting a crash when the game is loaded to around 77% on versions 1.19 and 1.20 of the game. The logs show a message about stack corruption, similar to #665.
Version 1.17 loads to the title screen, but then crashes instantly with a line about a mutex failure and "code 22".
To Reproduce
Steps to reproduce the behavior:
Click on "Play"
Wait for the game to load past 77%
See crash
Expected behavior
The game should run with no stack corruption issues.
Desktop (please complete the following information):
OS: Arch Linux ARM
Version: v0.10.0.47-AppImage-armhf (build 47)
Installation Type: AppImage
Additional context
I suspect that the issue is related to some kind of data corruption during the download, since deleting the Minecraft version and re-downloading it can start or stop the bug from happening on that version. My root filesystem is btrfs and a scrub shows no checksum errors, so this is not caused by a failing storage device.
The text was updated successfully, but these errors were encountered:
Describe the bug
I'm sometimes getting a crash when the game is loaded to around 77% on versions 1.19 and 1.20 of the game. The logs show a message about stack corruption, similar to #665.
Version 1.17 loads to the title screen, but then crashes instantly with a line about a mutex failure and "code 22".
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The game should run with no stack corruption issues.
Desktop (please complete the following information):
Additional context
I suspect that the issue is related to some kind of data corruption during the download, since deleting the Minecraft version and re-downloading it can start or stop the bug from happening on that version. My root filesystem is btrfs and a scrub shows no checksum errors, so this is not caused by a failing storage device.
The text was updated successfully, but these errors were encountered: