I'm not sure if it's the same problem but I'm seeing something similar. I can start a game and play for a while just fine. The only odd thing at the start of the game is that my screen is black until I first move the camera. However, at some point the game abruptly drops from about 60-80 fps down to 0-10. It hobbles along briefly but then crashes. This problem is with alpha 8 only, alpha 7 ran without any problems at all on the same machine.

Like weemcast I haven't been able to find something in particular to trigger this aside from just playing for an hour or so. I tried playing with a very small number of monsters and a small dungeon but didn't notice anything different from playing with a very large and complex dungeon and as many monsters as I could get. After seeing this post I tried running the game with the Windows Task Manager open at the same time but didn't see any obvious problems with memory use. It had a very small bump at the moment it crashed but otherwise stayed level while it ran.

The only other thing I noticed is that right before the fps tanks the minimap goes white and only shows the blue dot without any of the other features.

Specs: Fully patched version of Windows 8.1, 64 bit, i7, and a GTX 670.

I hope this is helpful.

It's happened every time so far. Like I said though, this only started for me with version 8.

Neither of the first two tests caused it to crash within an hour. I ran the tests with the same number/type of background applications I usually have open, just in case that was influencing the tests but even with that there wasn't any sign of a problem. However, when I tried playing a game as normal I had it crash just shy of two hours in, near turn 18,000. I'm going to repeat the first two tests for a longer period of time when I'm able.

As for the third test, I've tried but I keep catching swords with my face within the first few minutes so I might have to get better at adventure mode to really test it. Unless you mean to just leave it running?

If you could do #2 and leave it for a few hours that would be the best test.

I'll turn on my laptop and get this started now as well.

I ran the test two times, both for more than 18,000 turns, and didn't see a problem come up. At the end of both tests the frame rate was around 90 fps and the memory usage was nearly the same as it had been at the start. I did run these tests with aggressive enemies turned off which is different from how I normally play when I've seen this bug but I'm not sure if it could have an impact.

I played a normal keeper game (i.e. not just stay in a hole the whole time) without enemy aggression on and ran into the same problem. It was a lot later this time though, as it only started going down after turn 21,000 but I'm not sure if that's related to the enemy aggression or if I was just lucky this play-through.

I'm still really not sure what could be triggering it. It seems related to how long the game has been going but it has a pretty wide range of crash times. I've played with dungeons of varying complexity, armies of different sizes, and nothing obvious is jumping out at me. From what I recall after starting to keep track of these crashes I was never doing anything very interesting at the time, just general dungeon/army maintenance stuff.