Cryptic Studios games crash in some circumstances when Mumble overlay is enabled

[mumble-voip]

I'm sorry that at this time I don't have better details, as the crash reports frequently do not contain a mumble_ol DLL version numbers. Also, forum reports I've seen from customers are not incredibly detailed. I can inquire on the forums about the Mumble versions being used.

I have one crash dump with a mumble_ol.dll (not directly implicated in this particular crash) with a timestamp of "2-19-2011 2:44 PM" but I'm not sure if that's just a Windows file modification timestamp. MSVC reports the module info as follows:

mumble_ol.dll   *C:\Program Files (x86)\Mumble\mumble_ol.dll    N/A N/A No matching binary found.       63  0.00.0.0    2/19/2011 2:44 PM   6A430000-6A453000   CrashDump.mdmp: Native  

This ticket has been migrated from sourceforge. It is thus missing some details like original creator etc.
The original is at https://sourceforge.net/p/mumble/bugs/983/ .

[mumble-voip]

I tried reproducing on Win7 64, Nvidia 660M, with Nvidia drivers 295.93, 314 (.22?) and 320.00 BETA, with Mumble 1.2.3. This did not work. I was not actively using Mumble for voice, but I had to overlay enabled, and could see the the FPS meter and my name onscreen.

[Kissaki]

Looking at their website; for which of their games?
Which D3D Versions?

Sucks that we don’t have version numbers …
If it’s not a common problem I’d guess it’s older Mumble versions …

The 1.2.3 release version mumble_ol.dll has a Property "Date modified" of 19.02.2011 12:47 which would pretty much match the one from the crashdump.

[hacst]

Oh joy. Old overlay versions. We really have to release 1.2.4. There's some known issues with the overlay for 1.2.3 on windows 8. You didn't explicitly state the platform but if it was a windows 8 box I wouldn't look further.

[mumble-voip]

I have some information to add from a recent crash. I can provide a mini dump as well. It does appear to be from a Windows 8 machine, as the OS version is 6.2, build 9200.

Our engine has called IDirect3DDevice9::Reset to activate 1920x1080 60Hz fullscreen mode, and the device is currently lost. The app experienced a crash inside mumble_ol.dll, with a NULL pointer access violation.

The top two call stack entries above our Reset call are (note these are shown as offsets into Mumble_ol):

mumble_ol!0000f527()
mumble_ol!000101b3()

VC reports mumble_ol's module information as:

            mumble_ol.dll   *C:\Program Files (x86)\Mumble\mumble_ol.dll              N/A        N/A        No matching binary found.                                59           0.00.0.0                2/19/2011 2:44 PM          6D670000-6D693000        CrashDump.mdmp: Native

The access violation occurred here:

EAX = 6EEF2A8F EBX = 00000000 ECX = A0D0A0E9 EDX = 000002BB ESI = 00000000 EDI = 00000000 EIP = 6D67F527 ESP = 1075FAF0 EBP = 1075FB10 EFL = 00010212

6D67F520 55 push ebp
6D67F521 8B EC mov ebp,esp
6D67F523 83 EC 1C sub esp,1Ch
6D67F526 53 push ebx
6D67F527 8B 9E 4C 08 00 00 mov ebx,dword ptr [esi+84Ch]
6D67F52D 57 push edi
6D67F52E 85 DB test ebx,ebx
6D67F530 74 0D je 6D67F53F
6D67F532 68 F4 88 68 6D push 6D6888F4h
6D67F537 E8 E4 E0 FF FF call 6D67D620
6D67F53C 83 C4 04 add esp,4
6D67F53F FF 15 AC 60 68 6D call dword ptr ds:[6D6860ACh]
6D67F545 8D BE 3C 08 00 00 lea edi,[esi+83Ch]
6D67F54B 89 86 4C 08 00 00 mov dword ptr [esi+84Ch],eax
6D67F551 8B 07 mov eax,dword ptr [edi]
6D67F553 85 C0 test eax,eax
6D67F555 74 08 je 6D67F55F
6D67F557 8B 08 mov ecx,dword ptr [eax]
6D67F559 8B 51 08 mov edx,dword ptr [ecx+8]
6D67F55C 50 push eax
6D67F55D FF D2 call edx
6D67F55F 8B 86 38 08 00 00 mov eax,dword ptr [esi+838h]
6D67F565 8D 55 FC lea edx,[ebp-4]
6D67F568 52 push edx
6D67F569 C7 07 00 00 00 00 mov dword ptr [edi],0
6D67F56F C7 45 FC 00 00 00 00 mov dword ptr [ebp-4],0
6D67F576 8B 08 mov ecx,dword ptr [eax]
6D67F578 6A 01 push 1
6D67F57A 50 push eax
6D67F57B 8B 81 EC 00 00 00 mov eax,dword ptr [ecx+0ECh]
6D67F581 FF D0 call eax
6D67F583 8B 45 FC mov eax,dword ptr [ebp-4]
6D67F586 85 C0 test eax,eax
6D67F588 0F 84 1D 02 00 00 je 6D67F7AB
6D67F58E 8B 08 mov ecx,dword ptr [eax]
6D67F590 8B 51 10 mov edx,dword ptr [ecx+10h]
6D67F593 50 push eax
6D67F594 FF D2 call edx
6D67F596 8B 86 38 08 00 00 mov eax,dword ptr [esi+838h]
6D67F59C 8B 08 mov ecx,dword ptr [eax]
6D67F59E 8B 91 EC 00 00 00 mov edx,dword ptr [ecx+0ECh]
6D67F5A4 57 push edi
6D67F5A5 6A 01 push 1

Dave

[Krzmbrzl]

I kind of assume that this has been fixed in the meantime?

[no-response]

This issue has been automatically closed because there has been no response to our request for more information.
With only the information that is currently in the issue, we don't have enough information to take action.

Please reach out if you have or find the answers we need so that we can investigate further (or if you feel like this issue shouldn't be closed for another reason).