Unknown crash (no error report generated)

[Dragon]

I was playing today, trying out the new build, 3.1.8.8, and for no apparent reason, the game suddenly crashed.  No error report, no nothing, just a window message saying "this program has crashed".  I was expecting AI War to generate a crash report, so I just closed the windows box, but it wasn't a very useful box anyway.

I realize this isn't very helpful, but I figured I should let you know.  I'll see if it happens again...

I attached the save game my friend made when he saved after I crashed.  So it might not be useful, since it's made after the crash, so to speak.... but yeah...

[keith.lamothe]

Yea, not really much we can do with that  When you load the save, does it crash again?  Even if there's no error message, if we can get it to do it reliably I can generally find out why.

[x4000]

Having no error message is extremely suspect, though -- that means that not only did the game crash, but the entire .NET runtime actually died under it.  That could be something we did, but it's very hard to do that and I'm not sure I've really seen that directly.  You might try looking in your windows event log (Control Panel, Administrative Tools, Event Viewer) to see if there was anything of note there -- generally when .NET crashes, it is noted in either the system or application event logs in there.  Usually a crash like this is indicative of some problem other than the actual application itself that crashed, except as I said in rare cases when the application does something REALLY wrong.

[Dragon]

Ahhh, yes, that is it.  The event log shows:
 .NET Runtime version 2.0.50727.4952 - Fatal Execution Engine Error (6CEA851A) (80131506)

[x4000]

Yeah, that's what I figured.  That's almost impossible for "safe" code to do in .NET.  The only "unsafe" portions of the AI War are the ones that touch, via SlimDX, the DirectX components (and that's only because DirectX is "unsafe").  Please bear in mind that "safe" and "unsafe" might sound dangerous, but they are not.  Rather, it refers to the execution isolation of the program, and the ability of the program to affect the system at large, if that makes sense.

Anyway, sounds like something might be up with your .NET runtime v2, or else potentially just something else on the computer interfered with it momentarily, or there's a very remote possibility it was related to AI War, but it wouldn't be my first thought with most .NET programs, honestly.

Thanks for posting the error -- hope that helps!