-
Notifications
You must be signed in to change notification settings - Fork 4.3k
Mutagen crafting segfault #1171
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
Comments
Seems to happen with any recipe that uses spoilable items (and maybe others) from two different stacks. Not sure WHY, though. |
This happened when I tried to craft inactive turret while possessing two mysteriously de-stacked RAM items, which I attributed to my stubborn insistence of converting a 2 month old game through all the save-breaking commits. Seems like the same issue: (gdb) bt |
Yeah, that looks like the same stack trace I had, and inventory.cpp:846 is the same line as I had encountered. Okay, so it's ANY item that's split across multiple stacks, good to know. |
Okay, interesting finding: I set a breakpoint inside inventory::use_amount (the place where the actual crash is happening), and checked how many items in my inventory - 7. When I made vegetable soup, with the veggies spread across 2 stacks, items.size() == 6. When I made cooked veggies, with the exact same inventory contents (saved right before the crafting attempts), items.size() == 7. I don't think that's supposed to be happening. |
Mostly having crashes with vegetable material related cooking (Spaghetti Al Pesto is number 1 and Fruit-pies :'( game won't let me make them due to crashing. Having same items of different stacks of caused it to crash. |
Closed by #1268. |
If you have 2 stacks containing 2 tainted meats each, the mutagen crafting process will segfault. It looks as though it applies the iterator to the first stack, which then crashes after it has run through the two tainted meats in the first stack.
This doesn't seem to happen when crafting with components with charges though.
The text was updated successfully, but these errors were encountered: