Game hangs on exit and level completion

[iddq-tea]

Game version: 1.3.1.4778
System: Windows 10 64-bit

What happens: The game hangs when the game is exited or Space is pressed to return to the world map upon finishing a level. In case of the latter, the game autosaves before hanging and the next realm can be started when the game is re-launched without losing progress. While in its hung up state, all audio and repaint events halt. When the window is clicked, the usual "X has stopped working" box appears.

Reproduction rate: Does not seem to happen when the game is freshly launched, but happen somewhat consistently once the game has been running for a while. I am unable to provide exact numbers as I have not run any tests to force them. I have had around 12 hangs over the course of 4 days.

Steps to perform: While in-game: press ESC to bring up the settings, select the "Exit to menu" option. If the screen hangs on black, the game has stopped responding.

Here is the attacked crash log generated by Windows: Report.zip

The log file generated by the game did not contain anything that hints towards a critical error, but I since re-launched the game so it got overwritten.

[Loobinex]

Please attach a keeperfx.log file if it happens again.

[iddq-tea]

Was going to, but I accidentally overwrote it as I was writing the issue. Here is a fresh one, game hung on exit:

keeperfx.log

[Loobinex]

It's a longshot, but you could try updating to the latest alpha. There have been some changes in this area that might make a difference.

[iddq-tea]

It's a longshot, but you could try updating to the latest alpha. There have been some changes in this area that might make a difference.

Tried that, but my campaign progress got wiped entirely (except for unlocked secret levels) and my saves became incompatible, so my testing is non-conclusive:

I played through one of the free play levels, no problems occurred, but that made me think back - I don't actually recall the stable 1.5.1 version hanging during the free play levels or even the early campaign levels, the issues began popping up maybe 3-5 levels into the classic campaign. I'm not going to replay the campaign just to test if the issue still occurs in the alpha build, but it's something to consider that I didn't think about before.

[Loobinex]

ok, that's interesting information. I do not know how to act upon it at this point, but it is something.