-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Moving on certain worlds crashes the game with exit code 8 #14
Comments
I suppose you world is corrupted (Minecraft Bug) Same error code 8 appeared the third time, unknown cause. I had the same issue while testing, but Minecraft Version change maybe fix it itself. |
Speaking of world corruption, I suppose I could accept that that is the reason because the world was originally from 1.13.0.34 and because whenever I go to certain chunks it crashes the game however when I imported my world to my realms server everything worked fine without issues. It also worked fine when I imported to world to my phone. |
Well the gdb says its an Arithmetic exception (SIGFPE) some PC get it (my i7 8th gen gets it too(Ubuntu 19.04 amd64), but i5 3rd gen on MacOs not) |
Ignore it work only outside of gdb still not good, but it seems to work |
Update ignoring it isn't a Solution, its a really big floating point bug on x86 (not ARM)
|
Try this copy of your world https://drive.google.com/file/d/1fLjgRNyKAQEtgcDfiFhZvGSy0RPpQQXr/view?usp=drivesdk |
With my latest Experimental Patch Minecraft will not crash in your world (Linux only) (you posted, replaced fault by No Operation (0x90) on x86) It's workaround is included the latest Appimage https://github.com/ChristopherHX/linux-packaging-scripts/releases/tag/54.appimage |
It seems to be working fine. Will close this issue for now. |
The specific world can be found here: https://drive.google.com/open?id=1n0GOYAnE5kBB4UyXMa8abJEii0lpvoXX
The text was updated successfully, but these errors were encountered: