-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Segfault when opening uilist menus #76110
Comments
Yep, I'm getting the same issue. You can cause it with just about any healing item from what I am seeing. |
Reverting to 2024-08-31-2037 removes the crash, so somebody did something unwise. |
It looks like the below just needs to be wrapped in an Lines 135 to 136 in ea87d2d
It was wrapped in an if, it just seems to have gotten lost in the shuffle. |
Looks like a LOT of people are getting this, and I'm pretty confident in saying it is a real bug. So I'm just going to go ahead and pin it and shuffle everyone over to this issue. If you crash today when viewing a uilist and the stack trace mentions bad optional access... it's the same one as this. |
Adding the |
I don’t know how it got lost, but lost in the shuffle it was. I fixed it in #76157 though, because while I hadn’t seen this bug report I did happen to notice the problem while working on it. |
Looks like that should fix it. Well if it didn't I'm sure we'll get plenty more reports :) |
Describe the bug
After updating to the newest version, trying to heal yourself result in crashing.
The program has crashed.
See the log file for a stack trace.
CRASH LOG FILE: ./config/crash.log
VERSION: 0527e71
TYPE: class std::bad_optional_access
MESSAGE: Bad optional access
STACK TRACE:
Attach save file
San Pierre-trimmed.tar.gz
Steps to reproduce
Get yourself damaged, try to bandage yourself and got kicked out.
Expected behavior
No crashing
Screenshots
Versions and configuration
Dark Days Ahead [dda],
Disable NPC Needs [no_npc_food],
Portal Storms Ignore NPCs [personal_portal_storms],
Slowdown Fungal Growth [no_fungal_growth]
]
Additional context
No response
The text was updated successfully, but these errors were encountered: