[Rseding91] [1.1.8] Crash after interacting with SE mod gui during autosave

[wladekb]

I've been playing Space Exploration with a couple of other mods and did the following actions:

1. I have the spaceship console gui opened at the time autosave kicked in (it takes ~10 seconds to complete due to the size of the game)
2. During that time I discovered that the mod gui is interactive so I:
a) by accident checked "List destinations alphabetically" and unchecked it
b) selected a new destination
c) clicked Launch
3. When the autosave finished a message box popped up with the title "Notice" and the message "Index out of range"
4. After clicking the only button "Confirm" the gameplay terminated and the main menu showed up.

There's a mention of Exception in the logfile. Not sure if the save (176mb) is of any importance since the autosave loads and runs fine.

Code: Select all

6021.035 Error MainLoop.cpp:1282: Exception at tick 48438001: Index out of range.

factorio-index-out-of-range.png (805.86 KiB) Viewed 2002 times

factorio-current-index-out-of-range.log

(82.54 KiB) Downloaded 117 times

[boskid]

Error message tells almost nothing about the issue, save file and a way to reproduce it are required.

[wladekb]

Here is the save:

https://ufile.io/oxyev85m

Steps to reproduce:
1. Have the spaceship console gui opened (shown on the left side of the screen on the screenshot above). If not, click the blue spaceship console a bit to the left below the player position to bring it up.
2. Wait for an autosave to begin, then you need to complete steps 3-6 before the saving is finished
3. (maybe optional) Check the checkbox "List destinations alphabetically"
4. (maybe optional) Uncheck the checkbox "List destinations alphabetically"
5. Open the dropdown saying "5 matching locations" and click on "Calidus Orbit"
6. Click the Launch button below the dropdown.
7. Wait for an autosave to finish, the error pops up.

Note that completing the same actions without the autosave being executed works as expected.

[Rseding91]

Thanks for the report. It's now fixed for the next release.