[0.15.29] Paused server led to hard crash

[JCav]

A game my friend and I started back on 15.26 was updated from .28 to .29 today. I was hosting the game, when my friend tried to join and was given an error message regarding his version being .28 instead of the required .29.

I paused the server while he tried to get his game updated via Steam, and after he successfully did so, he attempted to rejoin while the game was still paused. This caused some sort of serious error in the program. I was unable to unpause. I was unable to quit the game gracefully. I had to kill the task via task manager.

I've never had a crash in Factorio before of any kind. I understand this may not be repeatable or a useful bug report, but it is all the information about the situation that I believe I have.

[Da-V-Man]

I have experienced this as well in .29 today while playing with a friend. I was hosting off of my own computer as opposed to a headless server, however. We were playing with mods at first, but then I tried hosting an un-modded game and we still had the same issue.

My OS is Windows 8.1

[deathsoverture]

Created an account to say I am having this same problem, 0.15.29 linux x64 headless, no mods.

[Loewchen]

Post the log, see my signature.

[Philip017]

i attempted to pause the server for someone to join, they joined, but the server would not unpause, and i had to restart the headless server.

this also caused my game to hard lock and i had to kill it in task manager.


EDIT: this could be related to: viewtopic.php?f=7&t=50854 one of the people in that topic attempted to join my server when the game crashed.

[EntroperZero]

Same problem here. Someone paused a server on which I'm an admin. On logging into the game, my UI is completely unresponsive, so I can't click the unpause button (or indeed, the quit button -- I have to End Task on Factorio).

[kovarex]

Thanks for the report, it is fixed for the next version.

[JCav]

Post the log, see my signature.

I wrongly assumed that since I had to end the task, that a logfile would not be present. Sorry for wasting your time.

Despite this being presumably fixed, I've attached the logfile as requested in case further information ends up necessary.

Sorry.