[.804 beta 2b][Freeze Crash -- Repeatable] Freeze when end turn, no obvious cause

EDITED IN CORRECTION:

CORRECTED REPORT: The game freezes even if I don't move onto the Inn.  Just hitting 'next turn' causes the freeze.  I tried a few things like moving the party elsewhere, stopping building construction, etc. and the freeze still occurred.  Have to CTL-ALT-DEL to get to task manager to shut down Elemental.


No memory dump or standard windows error message.

debug.err

save from immediately preceding this (just move party onto the humble Inn to induce)

dxdiag 32 bit

dxdiag 64 bit

 


[This is the original report: My party moves onto a Humble Inn tile and the game freezes.  No quest popup or the like, the freeze is immediate upon moving onto the tile.  ]

 

 

 

 

1,506 views 6 replies
Reply #1 Top

Correction -- the game freezes even if I don't move onto the Humble Inn.   It freezes if I just hit 'next turn'.  I tried a few things (stopped building construction, etc.) and it still froze. 

Editing original post and subject line to reflect this.

Reply #2 Top

How is it repeatable if you don't know the cause of it? I'm pretty sure repeatable means that you can start up a new game, do exactly the same things and have it crash on you again, not that it keeps happening within the same save.

Reply #3 Top

Quoting CdrRogdan, reply 2
How is it repeatable if you don't know the cause of it? I'm pretty sure repeatable means that you can start up a new game, do exactly the same things and have it crash on you again, not that it keeps happening within the same save.
End of CdrRogdan's quote

Repeatable means that the crash happens at the same point over and over. You may not know why it happens but you can predict when it will happen. He included a save file on the turn before the freeze and said running the turn would cause it to freeze again.

I had a similar problem when I submitted before. I could load the same save game over and over then press end turn button and it would freeze up at the end of that turn. I didn't know why it would freeze but I could repeat it over and over.

Reply #4 Top

I have had several games where after hitting end turn nothing happenned. I could still access cities, build units, etc., but not go to the next turn. The end turn just never reenabled.

Reply #5 Top

I had this issue in 2A and I was told that to be able to get around it load with "Cloth map only" enabled. This allowed me to play for several hundred more turns in 2A, however in 2B it seems that I was then afflicted with the "cannot end turn" bug that others are experiencing. This all may stem from whatever is being done to keep whatever currently seems to be eating folks system resources, and not turning them loose, at bay. However while it doesn't seem like everyone is hitting the old lock up after so many turns situation any more, those that aren't are still unable to progress farther into the game. They just don't have to force down a non responsive program. But hey, that's progress, and that's what these betas are all about. I can't lie though, the inability to research a few techs I consider essential from civ and war has me looking forward to 2C. I plan to start my next game with cloth map only enabled from the start, perhaps that will allow for a lot more game length, and if that brings me any joy I'll be sure and mention it in one of the plethora of threads that seem to be popping up regarding this issue or one similar.

Reply #6 Top

Just becuase it freezes at the same point over and over again within the same save does not make it repeatable. I don't mean to split hairs here, but claiming that something is repeatable implies that the programmers could load up their program, do exactly what you describe and have the test fail. In this case, exactly what he tried was 'clicking next turn' which doesn't happen for all instances of clicking next turn, and thus does not qualify as repeatable. In fact, repeatable in this report context only means that it is repeatable on your machine, so even if everything is done the same, it might still work on the programmers computers with different specs. That doesn't make the bug report useless or anything, just be careful about the terms you use.

The following excerpt might be helpful in posting good bug reports:

http://www.chiark.greenend.org.uk/~sgtatham/bugs.html

The section on 'I did it a moment ago' explains the difference between an intermitent fault and a repeatable one. (Mind you that most errors are repeatable - tied to some logic or other - but, without the information on how to repeat it, terming it as such can be misleading). Also it's somewhat prudent to shut down and restart your computer before confirming that something crashes every time you do something, as it might be due to a memory leak (from this or another program).