unhandled exception 0xC06D007E in wdll_delay_load.cpp:358 (__delayLoadHelper2)

[Philip Taylor]

Somebody just got the error:

Details: unhandled exception (Unknown (0xC06D007E))
Location: wdll_delay_load.cpp:358 (__delayLoadHelper2)

when running on 64-bit Windows 7. This looks like it's probably the same error as somebody else (whose name I forget) reported a while ago, where I think we discovered that the delay-loader was failing to load version.dll. But I don't think we ever found or solved the cause of that problem, and it appears it's affecting more people now.

[Jan Wassenberg]

Unfortunately we've not yet gotten closer to finding the cause, though I am in contact with Ismail/iso and trying to help debug.

Just a quick note for others who encounter this: you can work around the problem by launching with the -quickstart command line parameter (thus skipping the system detect code, which uses version.dll), though that will also disable sound.

[Philip Taylor]

Do we need to run this code at all? I vaguely remember that it was only used to detect OpenAL driver versions, and now we always use our bundled OpenAL Soft DLL so we're not interested in what version the user has. (Maybe I'm missing some other places this code is used, though?)

[Jan Wassenberg]

Good point, we no longer have to worry about the OpenAL version, but it's still very useful to see the graphics and also sound driver versions.

[Jan Wassenberg]

(In [7453]) disable delay-loading of version.dll. Of the delay-loaded DLLs, version.dll is the only one that is used in proximity to WoW64 FS redirection, which apparently has a dangerous interaction with delay-loading. This should prevent #484 (after update-workspaces + a rebuild), but we can't be sure due to lack of an x64 Vista or Win7 machine for testing. Can someone please confirm that it works without requiring the -quickstart workaround? refs #484

[EoD]

I just wanted to mention that the game ([7419]) started just fine on my 64-bit Windows 7 Professional machine without the -quickstart workaround. There should every 64-bit Windows machine be affected, shouldn't it?

[Jan Wassenberg]

Thanks for mentioning this! I'm glad to hear it works, but that's actually bad news in this case. The problem has been reported both on Vista and Win7, but my XP x64 machine doesn't run into difficulties, either.

I wonder if it might be related to Unicode special characters in the "system32" path (we had previously run into such difficulties with a localized "My Documents", where the characters weren't properly converted between UTF8 and UCS-2). That's not the case on your machine then, I take it?

[EoD]

I'm using an English version of Win7 x64 (6.1.7600), which has the default path C:\Windows\System32.

I also tried to change (all of) the regional settings to Japanese (+reboot). Just as well I copied the whole system32 folder to C:\𤭢system32 and changed the PATH variable accordingly (+reboot). And I renamed the folder of 0AD to 𤭢0ad-r07419-pre-alpha...

But nothing helped, the game always starts just fine! :)

[Jan Wassenberg]

Good idea, thanks for running those tests! So that's UTF8 trouble ruled out. I'm beginning to think we won't find the cause of this :S(especially due to the delay-load removal in r7453) But then again, maybe it'll happen as in #480 - after quite some time, we'll stumble upon the cause by pure happenstance.

[(none)]

Milestone Unclassified deleted

[historic_bruno]

This still relevant?

[Jan Wassenberg]

It's been 1 year, and I haven't seen any subsequent reports of problems in the forum either, so r7453 probably did fix it. I'll close this now, but please feel free to re-open if it comes up again.