All was going great until....

[Commander666]

So I'm at Sept 1/41. As Barbarossa is delayed there is nearly nothing happening as regards CPU load. No battles, only a few units moving. Game has been running fantastic.

Then all of a sudden I get this, which I never had before - ever.

And I can't get game to close in the quick launch bar. Trying everything, Next I get this. Game will not close/disappear from Quick Launch. . This is really stuck. How to proceed?

Can't abort, can't retry, can't ignore, and can't Close Window. Never has that happened before to me. Maybe restart computer?

 

[Pang Bingxun]

Use crtl + alt + del to start the task manager. It ought to be able to force abort any application.

 

[Commander666]

Restarting game I realize that the game crash happened with the monthly autosave. I better turn off auto-save as I have had no crashes otherwise (including manual saves).

Note: The application was no longer running. Therefore your advice would not work, would it? Going task bar icon I only have choice to close window (which it wouldn't do). Restarting worked fine.

Anyway, this is a big disappointment. What's gonna happen when game starts having some serious CPU use? Well, I'll find out soon enough as in 7 days a massive Barbarossa will launch.

 

[Pang Bingxun]

Note: The application was no longer running.

Your screenshots do indicate otherwise.

 

[Commander666]

OK, I guess you right. AoD was running even if it had crashed. Anyway, my computer jargon isn't really the issue. Rather the program crashing is. Any comment about that?

 

[Pang Bingxun]

This may well be a bug that should be reported. I recall that autosaves can be a bit of a problem. But have have never been able to reproduce this kind of crash. But admittedly, i have not been trying. Autosaves are really unconvenient, so i never use them in the first place.

 

[Commander666]

I consider it reported since you read in both forums. But I am amazed as 10 years of playing v1.02 to v1.09 never got that error. Yes, game often crashed but it was always "run-time error" and only when there was considerable CPU load as in many battles, supply map mode, or later circa to have more units. And yes, crashes were very often "save related" which is why I also disabled auto-saves.

But in this case, I am surprised because, IIRC, v1.10 had a lot of improvement regarding eliminating crashes, there was nearly no CPU load at the time, it is relatively early circa, and I was on terrain map. However, the error "std::terminate" is totally new in in experience. Anyway, yes, definitely disabled auto-saves.