FAF Client crashing in Vista

[SiliconKnight]

Trying Build 352. For reference, here is the data from the Windows Event viewer:

Level Date and Time Source Event ID Task Category
Error 3/14/2012 7:53:47 PM Application Error 1000 (100) Faulting application FAForever.exe, version 0.6.351.0, time stamp 0x49180193, faulting module kernel32.dll, version 6.0.6002.18449, time stamp 0x4da47967, exception code 0xe06d7363, fault offset 0x0003fc56, process id 0x1de8, application start time 0x01cd02460ae4e4c8.

Could this be something to do with Permissions, the weird pseudo-protection that Vista puts on the "Program Files" directory, UAC or something like that?

Some further research indicates that this same exception code (0xe06d7363) has been thrown for every crash of FAF all the way back to Build 341. That being said, I did a little digging and this link from MS has some info (not much):
http://support.microsoft.com/kb/185294

This link seems to give further details on how to troubleshoot this exception:
http://blogs.msdn.com/b/oldnewthing/archive/2010/07/30/10044061.aspx

[thygrrr]

And it's a protection fault, commonly known as a "crash"

It doesn't have anything to do with UAC. Some part of the C or C++ code behind the python stuff I am using is crashing, and I'm trying to find out what it is.

I wrote none of the code that's crashing, but I wrote code that calls that crashing code. So either I find out what is broken, and stop using it, or I replace it.

In this case, I replaced a DLL.

[SiliconKnight]

Thygrrr,

Thanks for the testing...I truly appreciate the extra time you are spending to assist. Unfortunately, this (*#^T@)*@ Vista machine just crashed again on build 352 (same exception as noted above). I hate inconsistent bugs...they are so difficult to track down!

[thygrrr]

Interesting I'll look into it some more the coming days.

[SiliconKnight]

I got it to load and submitted a bug report. Once it loads, it seems to be stable (after the first 5 secs or so). *sigh*

[thygrrr]

Okay, that means it's almost definitely the preview generation of the map images, and most likely FreeImage.dll (the dll I changed in the 352 test build) or the associated wrapper.

I'll look into it.

[Raging_Squirrel]

I got it to load and submitted a bug report.

didn't find anything on bitbucket
can you use pastebin to show us the log?

[thygrrr]

I got it to load and submitted a bug report.

didn't find anything on bitbucket
can you use pastebin to show us the log?

The crash is outside of FAF (probably in a dll), meaning Windows kills it before it can write anything to the log.

[thygrrr]

http://faforever.com/faf/FAForeverLobby-nopreviews.msi

Try this one. (you should not be seeing any map previews) Trying to narrow it down to the components that are likely to crash.

[SiliconKnight]

Well, I loaded it and got at least 12 starts in a row with no crashes, so maybe the map preview is what was crashing. I can live with this version, but if we could figure out how to include a fix in the regular code stream, that would be great.