[.981- .990] crash: 5 different ways, updated for .990

I started a new game, played one round, and then pressed Ctrl+N to try it out. Crash.

testing this for version .982:

1. starting a new game, saving immediately, exit to main menu and loading, saving again and rinse repeat. crash at the 6th iteration. dump and debug.err

2. starting a new game, repeated cntrl-n: crash at the 11th cntrl-n. debug.err (Note: before it crashed the picture at the "creating world" screen was black instead of showing a picture)

3 not tested yet

4. looking at my achievments gives me a crash: debug.err

5. Exiting the game and restarting within 2 seconds crashes the game.

Note: i did reinstall .981 completely (wiping game folders,  the folders in My Documents, and the ProgramData Folders, then running CCleaner.) For .982 i did only the update.

I've also noticed the issue when repeatedly loading the same save game that it will eventually crash like you mention in #1.

These are some great, repeatable crashes I hope the devs know about, especially since they are so easily repeatable.

I want to add this:

First time I start the game, it always crashes. After closing it, and restart, it executes fine. I had accepted as normal...but it should not be that.

I though that, if while it is loading, I change to other program, (like explroer, or whatever) could afect, but even if I do nothing, it crashes too the first time.

I find sometimes crashes when loading some savegames, but fortunately, that is less frequent, liek a corrupt save.

Biggest ones I've experianced was the ctrl-N crash and the load game while in game crash.

testing this for version .990: (deleted custom sovs, units and savegame before installing the patch)

1. starting a new game, saving immediately, exit to main menu and loading, saving again and rinse repeat. crash at the 4th iteration. dump and debug.err

1a. just loading the saved game crashed at the fifth load: dump and debug.err

2. starting a new game, repeated cntrl-n: crash at the 9th cntrl-n. debug.err (Note: at the 8th cntrl n the background picture at the "creating world" screen was black, it showed only the pic in the round circle)

2a. cntrl-n with a book open (starting story book or spell book): screen turns black with a few ui elements still showing, game hangs. After starting the task manager it crashed with a fatal error: DX ERROR:Invalid Call. debug.err here. Note: old thread with this issue here.

3 not played yet, so no oom crash yet

4. looking at my achievments gives me a crash: debug.err (there is a difference this time, the achievement window is now empty before it crashes, whereas it showed achievments in earlier versions before it crashed.

5. Exiting the game and restarting within 2 seconds doesnt crash the game anymore.

6. Starting a new game, then exiting to main menu and starting a new game again crashed after the 10th iterataion (here too with the "creating world" screen going black before it crashed): debug.err

The workaround for all those crashes (except the achievment crash) is exiting the game completely before doing any of those actions.

Makes me wonder if some threads aren't getting unlocked properly during the various reloads/restarts. Also, it would be interesting to watch memory usage while you do these things. Does it continue to rise?

ad 4. achievments crash is fixed

ad 3: i had 2 oom crashes in the last hour, so i am sure you have gotten the reports

I also have 1, 1a and 2 issues. I had CTDs in .980-.981, in later versions game become VERY slow (0.2-0.1 FPS or so), so I just press Alt+F4 to restart it. Usually I had graphics bugs like disappeared water in 2-3 save/load and unplayable game in 4-5 save/loads (or starting new game).

Also I had CTDs if I run game, Alt-Tab from it and leave it running in background for 2-3 hours.

You've updated to .992?

You may want to go back and edit your original post to cross out the crashes that appear to be fixed in the latest releases. It's hard to gauge progress otherwise.

Really? I suppose it could be the AI using background threads to calculate moves, but normally that would sound like a memory leak. Is that true for .992? They did a bunch of improvements with stability.