Weird crash in multiplayer
Taiyou06 opened this issue · 31 comments
Version information
mc1.18-0.4.0-alpha5+build.9
Reproduction Steps
1.Join a 1.18 server
2.Load a lot of chunks at once
2.1 or just wait few minutes
Crash Report file
crash-2021-12-02_18.29.27-client.txt
Additional information
No response
it's only happen with plugin "fartherviewdistance" wich is faking the server's render distance. completely natural in vanilla
Same issue
Crash report: https://crashy.net/WjYJQrDZB3E2QCus955w
I can reproduce this easily by going back and forth between two end gateways rapidly. Happens in singleplayer as well.
Does this issue still occur with version 0.4.1 for Minecraft 1.18.2?
Does this issue still occur with version 0.4.1 for Minecraft 1.18.2?
For me it still does.
The bug occurs in single player.
I can not accurately determine the sequence of actions leading to the crash.
It seems to have something to do with the teleportation of the player at the time of the light update in the chunks.
The bug occurs in single player. I can not accurately determine the sequence of actions leading to the crash. It seems to have something to do with the teleportation of the player at the time of the light update in the chunks.
Oh... for me it happen also in multiplayer
yeah...I have playing with friends with a 1.18.1 dungeon pve map, it's always crash my game while I dead. It indeed will teleport player after death. So I guess the problem is really related to teleporting. :/
I'm also using iris with shader pack.
so do we have any workaround here?
Alright, I'll say what I said on my own issue here.
I changed the code that throws the illegal state exception into a print and so far, it hasn't caused issues. So until an actual fix is pushed by someone who knows how sodium works, this might be useful to some people.
Here is a repository where I uploaded the code. I don't know the structure of sodium or the proper way I should have done this, checkout the master branch if you want to compile it yourself.
Here is the diff
Here is a repository where the binary is hosted; here is the jar you can use.
I hope this is acceptable - I understand that you don't want people posting binaries of forks in the issue tracker or something; on the other hand, please fix an apparently 6-month-old crash bug with an issue title and description that say nothing about the crash itself.
I tried to make a mod using mixin and modified the code to refresh the light source
Replace the original crashing code with console output
This problem seems to be fixed on my computer.
Here is the modrinth link for the mod
I can consistently reproduce this crash using a create contraption that moves me at extremely high speeds (literally a stick with a seat attached to one end and a mechanical bearing spinning it from the other). No matter what options i change it always happens
It happened to me when I set up 2 command blocks with buttons on them which teleport a player facing the button to the other command block. Holding right-click which means pushing the buttons constantly crashed the game with the same error
same issue
crash :
crash-2024-06-22_15.55.46-client.txt
@iKARY19 you've just got an old version of Indium that was not compatible with Fabric API 0.89 and above. You need to update Indium. You'll also need to update Sodium and any other dependent mods such as Sodium Extra and Iris
@Poopooracoocoo its doesent work its not compatible to other my mods
This is not a support forum, and your issue has nothing to do with what's described above. Use the Discord server if you want help from the community.