Alut Crash in Dec20 beta

[DustinClingman]

I recently updated to the December 20th build. After setting the try/catch blocks for the new OpenALException around ALut..alutInit() I got a hard crash.

Here was part of the dump:

An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : EXCEPTION_ACCESS_VIOLATION (0xc0000005) occurred at PC=0x77F69ECD
Function=RtlpWaitForCriticalSection+0x8A
Library=C:\Windows\System32\ntdll.dll

Before it blew up I got the "GO Team message" then it said it was entering alutInit with a device string set as null, then it blew up before my exception caught any problems.

After double checking my code, I rolled back to earlier versions of the libs and this problem went away with all apps functioning as they had previously.

Anyone else seen this one?

Dustin

[Athomas Goldberg]

Sorry for the delay getting back to you on this. I'll look into it ASAP