[Crash]: Client crashes upon reloading data
Not-February opened this issue ยท 3 comments
Steps to Reproduce the Crash
Every time that data needs to be reloaded(whether it is from the /reload command or simply leaving and then attempting to rejoin a single player world or remote server after having already loaded into a world once already), the game crashes as soon as the player opens their inventory.
Order of events to replicate:
- Launch game
- Join single player world
- Leave single player world
- Rejoin single player world
- Open inventory
Mod Pack URL (Optional)
Mod Pack Version (Optional)
No response
Extra Notes (Optional)
I'm pretty sure it's a niche mod conflict since I'm having trouble replicating the problem with just JEI + the included JEI addons I have installed.
ModernFix catches the crash and keeps the game open when it happens, but it's still impossible to load into a world and safely use your inventory until the game is fully restarted.
Interestingly enough, players who are actively using Dragon Survival - which replaces the default inventory interface with a different one - doesn't crash, but their inventory GUI gets screwed up in a totally different way:
It is also possible to open other inventory interfaces like chests without crashing, but they similarly render weirdly.
(Note that the above images reference EMI in the corner; I have it installed alongside JEI, but I've tested and confirmed that this problem happens without EMI installed as well)
So whatever the issue is, it only actually crashes if you are opening the default player inventory GUI but other inventories still get messed up either way.
Here's a gist of the debug.log if it helps in any way
Crash Report
https://gist.github.com/Not-February/ca2d4f591c48b7cc19df1d0b3416fe20
Thanks for the report!
Unfortunately I am not able to figure out what's wrong here from the log, but the newer versions of JEI might print some more info.
Can you please try with the latest version of JEI, and without JER and ModernFix?
If it still crashes, please let me see the new debug.log
I've tested the new version and it looks like this issue doesn't happen anymore. Thank you for the fix!