[2.0.43] Crash (Suspected corrupted save file) (Map::checkSegmentedUnitCountsConsistency)

[The God]

My game just crashes anytime I try to load one single world. It seems to have gotten corrupted as I've seen someone else report a similar case and get a comment saying it got corrupted.

It has happened after I have installed 3 mods: "Demolisher scales", "Demolisher Agriculture" and "Debloat-better-drill"
BUT it wasn't that now with those mods I can't use the world, since I installed these mods I removed them and tried again and again to load the world but it keeps giving me a message that the Minimally-active segmented units count doesn't match.

Only on this one world, if I make a new one with the same mods and even start off on vulcanus, the crash does not appear.

I have tried everything to recover the save file but even earlier auto saves do not work and instantly crash revealing the same error message.

Link to the post I found about pretty much the same issue: "126650"

I am using automatic updates and letting steam decide when to update so it should not be an issue of an out of date version of factorio.

[boskid]

I did a quick look at the corruption and it looks like one of the demolishers (segmented unit) became asleep without updating counters at all (one counter should go down and other should go up, none of that happened). Code looks bulletproof around segmented unit active state so without reproduction steps there is nothing to be fixed because there is no proof that anything is broken - so far this could be a hardware fault. I did a quick and dirty save file fix here but without identifying which demolisher incorrectly became asleep or if it went asleep correctly without updating counters, so there may be some artifacts from my fix.

128404-The Fulgorian Scrapper playthrough_fixed.zip

(12.11 MiB) Downloaded 35 times

[The God]

Thanks. Quick question though: How did it affect all previous autosaves of the playthrough? Was it an issue that started like a while ago and it just didn't check and crash until I had to load all future files?

Cause from a young programmers point of view (not very good at it, a hobbyist) it just makes no sense for me.

[boskid]

How did it affect all previous autosaves of the playthrough? Was it an issue that started like a while ago and it just didn't check and crash until I had to load all future files?

This corruption could easily survive saving and loading so it was possible all saves were corrupted, and it only started being noticed when game did a consistency check. Given that consistency checks are relatively expensive we do them only when you update game version or change composition of mods including versions of mods (unless you change hidden settings asking the game to do consistency checks always when loading a save file regardless of those conditions).

[The God]

Ah, well big thanks. Hopefully it will not happen again. Have a nice day