[2.0.28] A diverse bouquet of crashes when updating modded linux 2.0.23 save to any of the new versions

Things that has been reported already before.
dewayx
Burner Inserter
Burner Inserter
Posts: 7
Joined: Tue Dec 03, 2024 5:48 am
Contact:

[2.0.28] A diverse bouquet of crashes when updating modded linux 2.0.23 save to any of the new versions

Post by dewayx »

I tried updating my save (
tinyres 34.zip
Save file with mods activated
(50.83 MiB) Downloaded 15 times
), nothing works so far. I tried each version with and without mods enabled. Loading the save in 2.0.23 works, and I have the same issues when deactivating all mods in 2.0.23, saving, then trying all versions.
Funnily enough, each version manages to crash differently.

Linux Ubuntu 22.04.5
Crash reason summary:
2.0.24 - blueprints
2.0.25 - startup
2.0.26 - startup
2.0.27 - startup and SIGSEGV
2.0.28 - SIGSEGV
2.0.24
Crash when loading blueprints.

Code: Select all

  39.677 Info Scenario.cpp:178: Map version 2.0.23-0
  42.226 Loading blueprint storage: Local timestamp 1734753030, Cloud timestamp 1734753030
Factorio crashed. Generating symbolized stacktrace, please wait ...
(...)
  43.845 Error CargoStation.cpp:302: hatch was not true
  43.845 Error CrashHandler.cpp:643: Received 6
  Logger::writeStacktrace skipped.
  43.845 Error Util.cpp:95: Unexpected error occurred. If you're running the latest version (...) 
factorio-current-2-0-24.log
24 crashing on loading (blueprint load)
(27.96 KiB) Downloaded 12 times
2.0.25
Crash on startup, game doesn't even load. Log file included, but didn't even get to record any errors.
factorio-current-2-0-25.log
25 crashing on startup
(1.96 KiB) Downloaded 13 times
2.0.26
Same as 2.0.25
factorio-current-2-0-26.log
26 crashing on startup
(1.96 KiB) Downloaded 11 times
2.0.27
SIGSEGV error sometimes (see below 2.0.28), crash on startup some other times (both logs included)
factorio-current-2-0-27.log
27 crashing on loading (SIGSEGV)
(28.44 KiB) Downloaded 11 times
factorio-current-2-0-27-startup.log
27 crashing on startup
(1.96 KiB) Downloaded 12 times
2.0.28
SIGSEGV error

Code: Select all

  17.220 Info Scenario.cpp:178: Map version 2.0.23-0
  19.124 Error CrashHandler.cpp:641: Received SIGSEGV
Factorio crashed. Generating symbolized stacktrace, please wait ...
(...)
Stack trace logging done
  20.264 Error Util.cpp:95: Unexpected error occurred. If you're running the latest version (...)
factorio-current-2-0-28.log
28 crashing on loading (SIGSEGV)
(29.16 KiB) Downloaded 12 times
As of writing this post, 2.0.23 now decided to crash on startup too (it didn't before, didn't yesterday before updating and didn't today after reverting the first time).
Once I get it to run again, I'll add my mod list to the post. Otherwise - the save file should also contain the mods if you just sync and load.
Last edited by dewayx on Sat Dec 21, 2024 7:33 pm, edited 1 time in total.
dewayx
Burner Inserter
Burner Inserter
Posts: 7
Joined: Tue Dec 03, 2024 5:48 am
Contact:

Re: [2.0.28, 27, 26, 25, 24] A diverse bouquet of crashes when updating modded linux 2.0.23 save to any of the new versi

Post by dewayx »

Hey Loewchen, sorry but the CargoStation 2.0.24 error does not occur in 2.0.28, 124743 is only related to the 2.0.24 crash I encountered, not the 2.0.28 one.
Muche
Filter Inserter
Filter Inserter
Posts: 691
Joined: Fri Jun 02, 2017 6:20 pm
Contact:

Re: [2.0.28] A diverse bouquet of crashes when updating modded linux 2.0.23 save to any of the new versions

Post by Muche »

Your experience seems to match the one described in 124743.

In 2.0.24 you had "CargoStation.cpp:302: hatch was not true" (see 123802 Crash loading save working in 2.0.23 "CargoStation.cpp:302: hatch was not true"), fixed in 2.0.25.
Then you had "CargoHatch.hpp (25): CargoHatch::isValid() const, CargoStation.cpp (374): CargoStation::refreshCargoPodCapacity()", very similar to one in 124743 Crash loading save working in 2.0.23 "CargoStation.cpp(374): CargoStation::refreshCargoPodCapacity".
The difference might be due to your crash happening in a rocket silo, whereas theirs in a platform hub.
A dev would have to debug loading your save to confirm.
The conclusion was:
Rseding91 wrote: Thu Dec 19, 2024 2:02 pm Sorry, the underlying issue was fixed but the save is in a broken state and no migration was added. So until that happens (if it happens) the save won’t migrate or work correctly.
The startup crash looks to be a separate issue.
(I noticed some logs use integrated GPU, some don't. At the place your logs stop, my logs are detecting devices/controllers. No idea whether that's relevant.)
Post Reply

Return to “Duplicates”