[2.0.72] Crash during autosave when editing blueprint
Posted: Sat Jan 10, 2026 7:38 am
Mod List:
Elevated rails, Quality, and Space Age 2.0.72
flib 0.16.5
RateCalculator 3.3.7
EditorExtensions 2.5.2
visible-planets 1.6.1
angelsbioprocessinggraphics 2.0.0
angelspetrochemgraphics 2.0.0
angelsrefininggraphics 2.0.0
angelsmeltinggraphics 2.0.0
Note: I don't know why I have the 4 angels graphics mods, looks like I might have done an update at some point and enabled them
What did you do?
I was editing a blueprint, removing some belts, and then tried to save the blueprint.
What happened?
Next, I renamed autosave2.tmp.zip to .disabled, to force it not to load. Attempting to load autosave1.zip resulted in windows freezing and fully running out of memory, to the point explorer crashed.
Edit: After rebooting, autosave1.zip loaded fine. autosave2.tmp.zip still gave the I/O error. The blueprint I was editing did not save, it was the same as earlier.
My current theory is that there is an interaction between the autosave and either deleting an item or trying to save the blueprint.
What did you expect to happen instead? It might be obvious to you, but do it anyway!
I expected the blueprint to save.
Does it happen always, once, or sometimes?
Only once. I tried to edit the blueprint again, and was able to. I tried leaving the window open during an autosave, and it was fine. I tried to save the blueprint while the autosave window was active, but couldn't time it exactly.
I found this bug report when searching, it might be related, not sure. It mentioned autosaving and blueprints, but I was editing not deleting a blueprint. viewtopic.php?p=684951&hilit=crash+autosave#p684951
Elevated rails, Quality, and Space Age 2.0.72
flib 0.16.5
RateCalculator 3.3.7
EditorExtensions 2.5.2
visible-planets 1.6.1
angelsbioprocessinggraphics 2.0.0
angelspetrochemgraphics 2.0.0
angelsrefininggraphics 2.0.0
angelsmeltinggraphics 2.0.0
Note: I don't know why I have the 4 angels graphics mods, looks like I might have done an update at some point and enabled them
What did you do?
I was editing a blueprint, removing some belts, and then tried to save the blueprint.
What happened?
- At first, nothing happened, as in the blueprint window did not close, and the blueprint did not save.
- I am not sure the exact order of events, but the autosave window popped up. I am not sure if it appeared before, during, or after I clicked the "save blueprint" button.
- The autosave window did not disappear. This is a small test world, so it takes less than a second to save.
- I was able to move the blueprint window around, but additional clicks of the save button continued to do nothing.
- After about 20 seconds, the crash alert dialog appeared.
- After restarting the game, the autosave failed to open.
Next, I renamed autosave2.tmp.zip to .disabled, to force it not to load. Attempting to load autosave1.zip resulted in windows freezing and fully running out of memory, to the point explorer crashed.
Edit: After rebooting, autosave1.zip loaded fine. autosave2.tmp.zip still gave the I/O error. The blueprint I was editing did not save, it was the same as earlier.
My current theory is that there is an interaction between the autosave and either deleting an item or trying to save the blueprint.
What did you expect to happen instead? It might be obvious to you, but do it anyway!
I expected the blueprint to save.
Does it happen always, once, or sometimes?
Only once. I tried to edit the blueprint again, and was able to. I tried leaving the window open during an autosave, and it was fine. I tried to save the blueprint while the autosave window was active, but couldn't time it exactly.
I found this bug report when searching, it might be related, not sure. It mentioned autosaving and blueprints, but I was editing not deleting a blueprint. viewtopic.php?p=684951&hilit=crash+autosave#p684951