[BUG] Crash when Clicking "Task List" in Restaurant
anonymous563 opened this issue ยท 9 comments
Is there an existing issue for this?
- I have searched the existing issues
Are you using the latest MineColonies Verison?
- I am running the latest alpha version of MineColonies for my Minecraft version.
Did you check on the Wiki? or ask on Discord?
- I checked the MineColonies Wiki and made sure my issue is not covered there. Or I was sent from discord to open an issue here.
Minecraft Version
1.19.2
MineColonies Version
minecolonies-1.19.2-1.0.1378-ALPHA
Structurize Version
structurize-1.19.2-1.0.491-ALPHA
Related Mods and their Versions
domum_ornamentum-1.19-1.0.83-ALPHA-universal
Current Behavior
Clicking the task list button on the restaurant GUI causes the game to stop responding, forcing a crash to close it.
Expected Behavior
I should be able to see the tasks of the restaurant.
Reproduction Steps
Not sure, but:
Start colony, build level 3 restaurant in fortress style?
Hire cook and assistant cook.
Set a min stock in the restaurant for a bunch of cooked meats.
Click task list.
Logs
https://gist.github.com/anonymous563/a86c3b73f8e700b2d23af4fd9d3fc553
Anything else?
- Add a thumbs-up to the bug report if you are also affected. This helps the bug report become more visible to the team and doesn't clutter the comments.
- Add a comment if you have any insights or background information that isn't already part of the conversation.
Not sure what I did, but it doesn't crash anymore. If you see something I did in the crash log, please let me know.
It says the colony has a very big memory imprint? Again, happened when opening the restaurant task list. Minecraft stopped responding when I clicked it.
This crash happened again after closing Minecraft and reopening. I've waited several minutes, but it's still not responding.
@Raycoms please reopen!
Reproduction steps:
Load into single player world in my colony.
Click restaurant task list.
Watch "Not Responding" occur.
Could it be an issue with colony size?
#9093 (comment)
This is the crash log, no?