starred/mumble-mumble-voip

Fork 0

mirror of https://github.com/mumble-voip/mumble.git synced 2026-03-03 00:46:56 -05:00

1.4.0 snapshot 6 crashes because of opus.dll #2274

New issue

Closed

opened 2026-02-20 22:03:29 -05:00 by deekerman · 14 comments

deekerman commented

2026-02-20 22:03:29 -05:00

Owner

Originally created by @ViBE-HU on GitHub (Aug 4, 2021).

Originally assigned to: @davidebeatrici on GitHub.

Describe the bug
Referring to this I opened this issue. So if I'm not wrong 1.3.4 stable version uses Opus codec already and that build runs without any issue. I directly changed from that to the new snapshot and this build instantly crash when I start Mumble.

Steps to Reproduce
Steps to reproduce the behavior:

Start Mumble

Expected behavior
It should run.

Desktop (please complete the following information):

OS: Windows 10 Build 19043 (19041.vb_release.191206-1406)
Version: Mumble 1.4.0.191

Additional context
The affected machine is a Lenovo ThinkPad R61. It is an upgraded oddware with a Penryn based Intel Core 2 Duo T9300. While the motherboard is Meron based the only difference in specs is the SSE4.1 capability.

Originally created by @ViBE-HU on GitHub (Aug 4, 2021). Originally assigned to: @davidebeatrici on GitHub. **Describe the bug** Referring to [this](https://github.com/mumble-voip/mumble/issues/4932#issuecomment-892769855) I opened this issue. So if I'm not wrong 1.3.4 stable version uses Opus codec already and that build runs without any issue. I directly changed from that to the new snapshot and this build instantly crash when I start Mumble. **Steps to Reproduce** Steps to reproduce the behavior: 1. Start Mumble **Expected behavior** It should run. **Desktop (please complete the following information):** - OS: Windows 10 Build 19043 (19041.vb_release.191206-1406) - Version: Mumble 1.4.0.191 **Additional context** The affected machine is a Lenovo ThinkPad R61. It is an upgraded oddware with a Penryn based [Intel Core 2 Duo T9300](https://www.cpu-world.com/CPUs/Core_2/Intel-Core%202%20Duo%20Mobile%20T9300%20FF80576GG0606M%20(BX80576T9300).html). While the motherboard is Meron based the only difference in specs is the SSE4.1 capability.

deekerman

2026-02-20 22:03:29 -05:00

closed this issue
added the
build
label

deekerman commented

2026-02-20 22:03:31 -05:00

Author

Owner

@Kissaki commented on GitHub (Aug 6, 2021):

When the crash occurs the Mumble crash reporter opens and you submitted a crash report?

@Kissaki commented on GitHub (Aug 6, 2021): When the crash occurs the Mumble crash reporter opens and you submitted a crash report?

deekerman commented

2026-02-20 22:03:31 -05:00

Author

Owner

@Kissaki commented on GitHub (Aug 6, 2021):

If you can provide a stacktrace here that could be helpful too as a starting point for anyone looking into this.

@Kissaki commented on GitHub (Aug 6, 2021): If you can provide a stacktrace here that could be helpful too as a starting point for anyone looking into this.

deekerman commented

2026-02-20 22:03:31 -05:00

Author

Owner

@Krzmbrzl commented on GitHub (Aug 6, 2021):

Quoting from #4932:

The error log is

A hibát okozó alkalmazás neve: mumble.exe, verzió: 1.4.0.191, időbélyeg: 0x60a164a5
A hibát okozó modul neve: opus.dll, verzió: 0.0.0.0, időbélyeg: 0x60a16375
Kivételkód: 0xc000001d
Hiba pozíciója: 0x000000000001f350
A hibát okozó folyamat azonosítója: 0x17ec
A hibát okozó alkalmazás indításának időpontja: 0x01d789245c117909
A hibát okozó alkalmazás elérési útja: C:\Program Files\Mumble\client\mumble.exe
A hibát okozó modul elérési útja: C:\Program Files\Mumble\client\opus.dll
Jelentés azonosítója: ef84c957-293f-4e96-82b0-72ce94f17bb0
A hibát okozó csomag teljes neve: 
A hibát okozó csomag relatív alkalmazásazonosítója:

which google-translates to

The name of the application that is causing the error: mumble.exe, version: 1.4.0.191, timestamp: 0x60a164a5
The name of the module causing the error: opus.dll, version: 0.0.0.0, timestamp: 0x60a16375
Exception code: 0xc000001d
Error position: 0x000000000001f350
The ID of the process that caused the error: 0x17ec
The time that started the application that is causing the error is 0x01d789245c117909
The path to the application that is causing the error is C: \ Program Files \ Mumble \ client \ mumble.exe
The path to the module that is causing the error is C: \ Program Files \ Mumble \ client \ opus.dll
Report ID: ef84c957-293f-4e96-82b0-72ce94f17bb0
Full name of the package causing the error:
Relative application ID of the package causing the error:

Error code 0xc000001d seems to be "Illegal instruction" (see https://stackoverflow.com/questions/44231673/debugging-0xc000001d-exception-with-windbg) meaning that your CPU does not support some instruction that seems to be used inside the Opus library.

From this post it seems that this is probably because on the machine we build our windows bianries there are some CPU instructions that are not available on your computer and therefore it fails.
I think in order to figure out how to proceed with this, we'll have to figure out what instruction is the issue exactly.
@Kissaki or @davidebeatrici does one of you have experience with figuring this out based on the given memory address? 🤔

@Krzmbrzl commented on GitHub (Aug 6, 2021): Quoting from #4932: The error log is ``` A hibát okozó alkalmazás neve: mumble.exe, verzió: 1.4.0.191, időbélyeg: 0x60a164a5 A hibát okozó modul neve: opus.dll, verzió: 0.0.0.0, időbélyeg: 0x60a16375 Kivételkód: 0xc000001d Hiba pozíciója: 0x000000000001f350 A hibát okozó folyamat azonosítója: 0x17ec A hibát okozó alkalmazás indításának időpontja: 0x01d789245c117909 A hibát okozó alkalmazás elérési útja: C:\Program Files\Mumble\client\mumble.exe A hibát okozó modul elérési útja: C:\Program Files\Mumble\client\opus.dll Jelentés azonosítója: ef84c957-293f-4e96-82b0-72ce94f17bb0 A hibát okozó csomag teljes neve: A hibát okozó csomag relatív alkalmazásazonosítója: ``` which google-translates to ``` The name of the application that is causing the error: mumble.exe, version: 1.4.0.191, timestamp: 0x60a164a5 The name of the module causing the error: opus.dll, version: 0.0.0.0, timestamp: 0x60a16375 Exception code: 0xc000001d Error position: 0x000000000001f350 The ID of the process that caused the error: 0x17ec The time that started the application that is causing the error is 0x01d789245c117909 The path to the application that is causing the error is C: \ Program Files \ Mumble \ client \ mumble.exe The path to the module that is causing the error is C: \ Program Files \ Mumble \ client \ opus.dll Report ID: ef84c957-293f-4e96-82b0-72ce94f17bb0 Full name of the package causing the error: Relative application ID of the package causing the error: ``` Error code 0xc000001d seems to be "Illegal instruction" (see https://stackoverflow.com/questions/44231673/debugging-0xc000001d-exception-with-windbg) meaning that your CPU does not support some instruction that seems to be used inside the Opus library. From [this post](https://stackoverflow.com/questions/47899971/c-getting-error-illegal-instruction-core-dumped-upon-bitwise-or-operatio) it seems that this is probably because on the machine we build our windows bianries there are some CPU instructions that are not available on your computer and therefore it fails. I think in order to figure out how to proceed with this, we'll have to figure out what instruction is the issue exactly. @Kissaki or @davidebeatrici does one of you have experience with figuring this out based on the given memory address? :thinking:

deekerman commented

2026-02-20 22:03:31 -05:00

Author

Owner

@ViBE-HU commented on GitHub (Aug 6, 2021):

When the crash occurs the Mumble crash reporter opens and you submitted a crash report?

yes it opens but @Krzmbrzl told that feature is dead. so i did not sent the report.

@ViBE-HU commented on GitHub (Aug 6, 2021): > When the crash occurs the Mumble crash reporter opens and you submitted a crash report? yes it opens but @Krzmbrzl told that feature is dead. so i did not sent the report.

deekerman commented

2026-02-20 22:03:32 -05:00

Author

Owner

@Kissaki commented on GitHub (Aug 9, 2021):

If it’s actually CPU instructions compiled with but not supported my first suspect would be the SSE/SSE2 extensions.

As you asked for it, my assumptions would be as follows:

if Error position: 0x000000000001f350 indicates the memory or dll offset (which may be the same), then it should be discoverable while running, with a debugger, or maybe even from the dll itself.

A stacktrace may be very helpful though to get the function (maybe even the context may be useful) that contains the unsupported CPU instruction. Given that no stacktrace was posted above, the dump - which contains the stacktrace - would be very helpful to debug it - especially with the instruction pointer at the correct address already, which should simplify discovery.

What kind of CPU are you using @ViBE-HU ?

The easiest approach may be to check the CPU for supported CPU instruction sets and simply compile a test version for ViBE to try out without it. As I said before, if this is actually the issue, SSE2 seems very likely (which has been common for a long time, but may still be missing on still used older CPUs). Otherwise, we should be able to discover which instruction sets are supported and not supported here.

@Kissaki commented on GitHub (Aug 9, 2021): If it’s actually CPU instructions compiled with but not supported my first suspect would be the SSE/SSE2 extensions. As you asked for it, my assumptions would be as follows: if `Error position: 0x000000000001f350` indicates the memory or dll offset (which may be the same), then it should be discoverable while running, with a debugger, or maybe even from the dll itself. A stacktrace may be very helpful though to get the function (maybe even the context may be useful) that contains the unsupported CPU instruction. Given that no stacktrace was posted above, the dump - which contains the stacktrace - would be very helpful to debug it - especially with the instruction pointer at the correct address already, which should simplify discovery. What kind of CPU are you using @ViBE-HU ? The easiest approach may be to check the CPU for supported CPU instruction sets and simply compile a test version for ViBE to try out without it. As I said before, if this is actually the issue, SSE2 seems very likely (which has been common for a long time, but may still be missing on still used older CPUs). Otherwise, we should be able to discover which instruction sets are supported and not supported here.

deekerman commented

2026-02-20 22:03:32 -05:00

Author

Owner

@ViBE-HU commented on GitHub (Aug 9, 2021):

i mentioned in the additional infos that the CPU is an Intel Core 2 Duo T9300.

@ViBE-HU commented on GitHub (Aug 9, 2021): i mentioned in the additional infos that the CPU is an [Intel Core 2 Duo T9300](https://www.cpu-world.com/CPUs/Core_2/Intel-Core%202%20Duo%20Mobile%20T9300%20FF80576GG0606M%20(BX80576T9300).html).

deekerman commented

2026-02-20 22:03:32 -05:00

Author

Owner

@davidebeatrici commented on GitHub (Aug 9, 2021):

Reproduced on an Arrandale Intel Core i5.

Opus is probably attempting to use the AVX instruction set because it relies on what the machine it is compiled on supports.

@davidebeatrici commented on GitHub (Aug 9, 2021): Reproduced on an [Arrandale](https://ark.intel.com/content/www/us/en/ark/products/codename/32724/products-formerly-arrandale.html) Intel Core i5. Opus is probably attempting to use the AVX instruction set because it relies on what the machine it is compiled on supports.

deekerman commented

2026-02-20 22:03:32 -05:00

Author

Owner

@davidebeatrici commented on GitHub (Aug 9, 2021):

@ViBE-HU The binary built from CI in #5229 should work.

@davidebeatrici commented on GitHub (Aug 9, 2021): @ViBE-HU The binary built from CI in #5229 should work.

deekerman commented

2026-02-20 22:03:32 -05:00

Author

Owner

@ViBE-HU commented on GitHub (Aug 9, 2021):

cool. do i have to test?

@ViBE-HU commented on GitHub (Aug 9, 2021): cool. do i have to test?

deekerman commented

2026-02-20 22:03:32 -05:00

Author

Owner

@davidebeatrici commented on GitHub (Aug 9, 2021):

That would be great, thanks!

@davidebeatrici commented on GitHub (Aug 9, 2021): That would be great, thanks!

deekerman commented

2026-02-20 22:03:32 -05:00

Author

Owner

@ViBE-HU commented on GitHub (Aug 10, 2021):

where can i download the Windows x64 build?

@ViBE-HU commented on GitHub (Aug 10, 2021): where can i download the Windows x64 build?

deekerman commented

2026-02-20 22:03:32 -05:00

Author

Owner

@davidebeatrici commented on GitHub (Aug 10, 2021):

https://dev.azure.com/Mumble-VoIP/Mumble/_build/results?buildId=5158&view=artifacts&pathAsName=false&type=publishedArtifacts

@davidebeatrici commented on GitHub (Aug 10, 2021): https://dev.azure.com/Mumble-VoIP/Mumble/_build/results?buildId=5158&view=artifacts&pathAsName=false&type=publishedArtifacts

deekerman commented

2026-02-20 22:03:32 -05:00

Author

Owner

@ViBE-HU commented on GitHub (Aug 10, 2021):

it's working. thanks. but i had to start it for a few times. first it started with english without any error messages. then i changed the language and it won't started automatically. i tried to start it again but nothing happened. i checked the the task manager and looks like the application does not even stopped. it was stuck in the background and generated an event in the system log because of the mumble_app.dll as i mentioned before. if i kill the process the application will starts normally with the selected language.

the actual log:

A hibát okozó alkalmazás neve: mumble.exe, verzió: 1.5.0.0, időbélyeg: 0x6111b57f
A hibát okozó modul neve: mumble_app.dll, verzió: 1.5.0.0, időbélyeg: 0x6111b57b
Kivételkód: 0xc0000005
Hiba pozíciója: 0x0000000000e8c43e
A hibát okozó folyamat azonosítója: 0x25a0
A hibát okozó alkalmazás indításának időpontja: 0x01d78ddc4288595e
A hibát okozó alkalmazás elérési útja: C:\Program Files\Mumble\client\mumble.exe
A hibát okozó modul elérési útja: C:\Program Files\Mumble\client\mumble_app.dll
Jelentés azonosítója: c5a0fb4b-7d71-4772-8cfb-32cfbebf973a
A hibát okozó csomag teljes neve: 
A hibát okozó csomag relatív alkalmazásazonosítója:

@ViBE-HU commented on GitHub (Aug 10, 2021): it's working. thanks. but i had to start it for a few times. first it started with english without any error messages. then i changed the language and it won't started automatically. i tried to start it again but nothing happened. i checked the the task manager and looks like the application does not even stopped. it was stuck in the background and generated an event in the system log because of the mumble_app.dll [as i mentioned](https://github.com/mumble-voip/mumble/issues/4932#issuecomment-892667812) before. if i kill the process the application will starts normally with the selected language. the actual log: ``` A hibát okozó alkalmazás neve: mumble.exe, verzió: 1.5.0.0, időbélyeg: 0x6111b57f A hibát okozó modul neve: mumble_app.dll, verzió: 1.5.0.0, időbélyeg: 0x6111b57b Kivételkód: 0xc0000005 Hiba pozíciója: 0x0000000000e8c43e A hibát okozó folyamat azonosítója: 0x25a0 A hibát okozó alkalmazás indításának időpontja: 0x01d78ddc4288595e A hibát okozó alkalmazás elérési útja: C:\Program Files\Mumble\client\mumble.exe A hibát okozó modul elérési útja: C:\Program Files\Mumble\client\mumble_app.dll Jelentés azonosítója: c5a0fb4b-7d71-4772-8cfb-32cfbebf973a A hibát okozó csomag teljes neve: A hibát okozó csomag relatív alkalmazásazonosítója: ```

deekerman commented

2026-02-20 22:03:32 -05:00

Author

Owner

@Krzmbrzl commented on GitHub (Aug 10, 2021):

I think what you are seeing now is #4932

@Krzmbrzl commented on GitHub (Aug 10, 2021): I think what you are seeing now is #4932