Mumble 1.4.287 will not launch on Windows 10

[evanbishop]

The issue

After updating from Mumble 1.3.X to 1.4.287, Mumble will no longer load. Attempting to launch Mumble results in the process immediately dying. I tried deleting files in AppData, uninstalling and reinstalling, and can't get it to launch. Launching from cmd provides no messages either; it just dies instantly.

Mumble version

1.4.287

Mumble component

Client

OS

Windows

Additional information

No response

[Krzmbrzl]

Do you have the Visual C++ Redistributable installed? (See download page on our website)

[evanbishop]

Yes, I have the Visual C++ Redistributable installed. I have the x86 and x64 versions of the 2008, 2010, 2012, 2013, and 2015-2022.

[Krzmbrzl]

Hm... this is odd. I don't think I ever encountered a situation such as this...

@davidebeatrici any ideas?

[davidebeatrici]

I would take a look at the console log (%AppData%\Mumble\Mumble\Console.txt), if it exists.

[evanbishop]

The contents of the console log are:

<W>2022-11-18 15:23:53.697 G15LCDEngine_lglcd: Logitech LCD Manager not detected.
<D>2022-11-18 15:23:53.713 libopus 1.3.1-97-g6b6035ae from C:/Program Files/Mumble/client/opus.dll
<W>2022-11-18 15:23:53.728 CELT bitstream 8000000b from C:/Program Files/Mumble/client/celt0.0.7.0.dll

and that's it..

[davidebeatrici]

What processor does your computer have?

[evanbishop]

I have a Ryzen 5 3600X.

I may have some free time tomorrow to set up a build and debug environment for Mumble. I've never developed for or on Windows before, though (just Linux)

[davidebeatrici]

Okay, we can exclude unsupported instruction sets as the cause.

Build instructions can be found here: https://github.com/mumble-voip/mumble/blob/master/docs/dev/build-instructions/build_windows.md

[github-actions]

As there has been no activity on this issue for a couple of days, we assume that your issue has been fixed in the meantime.
Should this not be the case, please let us know.

If no further activity happens, this issue will be closed within 3 days.

[evanbishop]

Hello. I am still having this issue. I've been having some trouble setting up a build environment due to issues resolving dependencies so it ended up on the back burner. I'm going to give it another shot today.

[davidebeatrici]

No problem, did you perhaps encounter microsoft/vcpkg#27758?

[evanbishop]

Yes, that's the one! I was able to check out this branch microsoft/vcpkg#27974 and get going

[evanbishop]

I was able to build and debug mumble with the issue. What kills mumble is:

Exception thrown at 0x0000000069A2F26B (libjack64.dll) in mumble.exe: 0xC0000005: Access violation reading location 0xFFFFFFFFD9681F5E.

I wonder if I've hit jackaudio/jack2#275. I'll keep debugging maybe tomorrow, I'm going to go spend some time with my family. Happy thanksgiving all :)

[davidebeatrici]

Excellent, you indeed found the culprit!

Update JACK and the application should launch successfully.

[evanbishop]

Updating JACK did indeed solve the problem. The thing is, I don't recall ever installing JACK nor was it listed in the list of installed programs., it must have been installed as a dependency of something else, or maybe I had it laying around for a few years and forgot about it.

Regardless, I'm wondering if there's any way for Mumble to detect and warn the user about this condition? I'm totally inexperienced in Windows development, but if this is something that's feasible I'd be more than willing to take a shot at it in my spare time to save someone else the trouble later of wondering why Mumble seems broken.

[davidebeatrici]

In theory we can retrieve JACK's version from the DLL's metadata, allowing us to reject anything older than the first good version.

[github-actions]

As there has been no activity on this issue for a couple of days, we assume that your issue has been fixed in the meantime.
Should this not be the case, please let us know.

If no further activity happens, this issue will be closed within 3 days.

[Krzmbrzl]

Closing this in favor of #6135