[2.0.57] Crash when spoiling in an assembling machine

[boomshroom]

After running in my main save for a bit, Factorio seemed to spontaneously crash with no apparent cause. The stack trace in the log suggests that something in an assembling machine (prototype, not necessarily a normal assembler) spoiled and failed to get moved to a trash slot, resulting in a segfault. It's likely that the segfault is that the trash slot didn't exist in the prototype and was set to null. I was able to replicate the crash after loading an autosave, where it happened on the exact same world tick as the first time.

Since it didn't occur before, it's possible that the crash is related to the change in behavior for inserters inserting spoilage into captive biter spawners.

Unfortunately, I am unsure of which item spoiled nor in which machine, so the best I can do is share my entire main save file. I have also been using many mods, including various custom patches, and a mod or two present locally that isn't on the portal. I'm uncertain how I can force Factorio to load only with officially published mods, but hopefully the crash would still happen as none of the local patches add additional items, machines, or recipes. If not, at least I can provide the backtrace along with the rest of the log.

As it is a segfault, I should also mention that I am running the game through Steam on Linux 6.15.0, NixOS 25.11, X86_64. This probably isn't needed, but better save than sorry.

Save file: https://drive.google.com/file/d/16yC7yK ... sp=sharing

Backtrace:

Code: Select all

1118.971 Error CrashHandler.cpp:641: Received SIGSEGV
Factorio crashed. Generating symbolized stacktrace, please wait ...
src/Util/StacktraceToStream.cpp (52): walkStackAndPrintToStream
src/Util/StacktraceToStream.cpp (60): printStacktraceToStream
src/Util/Logger.cpp (334): writeStacktrace
src/Util/Logger.cpp (379): logStacktrace
src/Util/CrashHandler.cpp (181): writeStackTrace
src/Util/CrashHandler.cpp (644): commonSignalHandler
src/Util/CrashHandler.cpp (652): SignalHandler
0x7fa01f24146f
src/Entity/CraftingMachine.cpp (1458): fallbackToTrashSlots
src/Entity/CraftingMachine.cpp (946): onStackSpoiled
src/Item/ItemStack.cpp (707): spoil
src/Item/Item.cpp (63): spoil
src/Item/ItemSpoilQueue.cpp (115): updateBuckets
src/Item/ItemSpoilQueue.cpp (92): update
src/Map/Map.cpp (1357): updateEntities
src/Map/Map.cpp (1251): update
src/Game.cpp (175): update
src/Scenario/Scenario.cpp (1217): update
src/Scenario/Scenario.cpp (1130): updateStep
src/MainLoop.cpp (1477): gameUpdateStep
src/MainLoop.cpp (1272): gameUpdateLoop
/opt/gcc-13.2.0/lib/gcc/x86_64-pc-linux-gnu/13.2.0/../../../../include/c++/13.2.0/bits/std_function.h (591): operator()
src/Util/WorkerThread.cpp (70): loop
/tmp/tmp.dlP10F34z6/objdir/../gcc-13.2.0/libstdc++-v3/src/c++11/thread.cc (104): execute_native_thread_routine
start_thread
__clone3
0xffffffffffffffff
Stack trace logging done
1121.807 Error CrashHandler.cpp:190: Map tick at moment of crash: 86290098

1. What did I do
   • Seemingly nothing while an item somewhere in the factory spoils
2. What happened
   • Segmentation fault
3. What did I expect to happen instead?
   • The game to keep running normally while the item that spoiled silently gets moved to its machine's trash slot to be taken away somewhere
4. Does it happen always, once, or sometimes?
   • I attempted to replicate it once, and it crashed on the exact same world tick as the first time

[boskid]

Thanks for the report. I was already aware of this crash due to automatic crash log uploads and its fixed for 2.0.58. Specifically for this crash to happen, an item needs to spoil in the source inventory while crafter has no recipe set. This only happens in case of furnaces since assembling machine does not allow having items in source inventory while the recipe is not configured.

[boomshroom]

Thank you for the quick response. I wasn't certain if you'd actually received an automated crash log, and I didn't see any other thread for it, so I figured I should making an account and report regardless.

If that's the requirement, then the culprit was would've most likely been Cubium and `destabilized-cube-matter-recycling`, which takes 2 `destabilized-cube-matter` in a recycler, but `destabilized-cube-matter` can also spoil into `dream`. With that information, I could probably find the recycler with this and remove the item from its input before it spoils.