Hangs on launch

[theebu]

Whenever I launch the program, it 'hangs'. I say it like that because when I mouse-over the windows, I get the busy cursor. However when I open Taskmanager, it shows the program has NOT crashed, and it isn't eating up any resources. It never actually crashes. I've tried several different installs from different versions, and even uninstalled most programs incase there was a conflict somewhere.

Not sure how to proceed from here.

To note, on Win 7 64-bit. 8g DDR3 ram. I5 quad-core, 3.0

Never had an issue with it before, just randomly stopped.

[kissaki]

Not any resources, so 0 MB memory usage?

Check the log

%APPDATA%/Mumble/Console.txt

[theebu]

Sorry, by not eating resources I meant it wasn't using any more than normal.

 

<W>2013-10-19 21:15:26.716 DirectSound: Disabled as WASAPI is available
<W>2013-10-19 21:15:26.716 ASIO: No valid devices found, disabling
<W>2013-10-19 21:15:26.731 CELT bitstream 8000000b from C:/Program Files (x86)/Mumble/celt0.0.7.0.sse2.dll
<W>2013-10-19 21:15:26.741 CELT bitstream 80000010 from C:/Program Files (x86)/Mumble/celt0.0.11.0.sse2.dll
<W>2013-10-19 21:15:26.741 Locale is en_US
<W>2013-10-19 21:15:26.781 Database SQLite: "3.6.19" 
<W>2013-10-19 21:15:26.782 Bonjour: Failed to load dnssd.dll
<W>2013-10-19 21:15:26.915 Overlay: Listening on "\\.\pipe\MumbleOverlayPipe" 
<W>2013-10-19 21:15:27.365 Adding device {6f1d2b60-d5a0-11cf-bfc7-444553540000} Mouse Mouse:8
<W>2013-10-19 21:15:27.379 Adding device {6f1d2b61-d5a0-11cf-bfc7-444553540000} Keyboard Keyboard:127
<W>2013-10-19 21:15:27.389 Adding device {fbb0f180-167c-11e3-8001-444553540000} 6 axis 24 button device with hat switch 6 axis 24 button device with hat switch:24
<W>2013-10-19 21:15:27.403 Adding device {45f776f0-1674-11e3-8001-444553540000} T.Flight Hotas X T.Flight Hotas X:12
<W>2013-10-19 21:15:27.437 Adding device {45f79e00-1674-11e3-8002-444553540000} G700 Laser Mouse G700 Laser Mouse:767
<W>2013-10-19 21:15:27.469 AudioInput: 40000 bits/s, 48000 hz, 480 sample CELT
<W>2013-10-19 21:15:27.471 WASAPIInput: Failed to open selected input device {0.0.1.00000000}.{852be1f2-1b88-4d4e-82b4-e04a6a70d219} {0.0.1.00000000}.{852be1f2-1b88-4d4e-82b4-e04a6a70d219} (hr=0x80070490), falling back to default
<W>2013-10-19 21:15:27.471 WASAPIOutput: Failed to open selected input device (hr=0x80070490), falling back to default
<W>2013-10-19 21:15:27.474 WASAPIInput: Latencies 100000 30000 => 100000
<W>2013-10-19 21:15:27.474 WASAPIOutput: Latencies 100000 30000 => 100000
<W>2013-10-19 21:15:27.477 WASAPIInput: Stream Latency 40000 (320)
<W>2013-10-19 21:15:27.478 AudioInput: Initialized mixer for 1 channel 16000 hz mic and 0 channel 48000 hz echo
<W>2013-10-19 21:15:27.480 WASAPIOutput: Stream Latency 116100 (2646)
<W>2013-10-19 21:15:27.480 WASAPIOutput: Periods 10000us 3000us (latency 11610us)
<W>2013-10-19 21:15:27.481 WASAPIOutput: Buffer is 60000us (5)
<W>2013-10-19 21:15:27.481 AudioOutput: Initialized 2 channel 44100 hz mixer
<W>2013-10-19 21:15:27.632 Adding device {729294f0-1684-11e3-8002-444553540000} Wireless Stereo Headset Wireless Stereo Headset:4096
<W>2013-10-19 21:15:27.732 Adding device {45f83a40-1674-11e3-8005-444553540000} SWTOR Gaming Keyboard by Razer SWTOR Gaming Keyboard by Razer:573
<W>2013-10-19 21:15:27.760 Adding device {45f8af70-1674-11e3-8006-444553540000} SWTOR Gaming Keyboard by Razer SWTOR Gaming Keyboard by Razer:3
<W>2013-10-19 21:15:27.786 Adding device {45f8af70-1674-11e3-8007-444553540000} SWTOR Gaming Keyboard by Razer SWTOR Gaming Keyboard by Razer:1
<W>2013-10-19 21:15:27.814 Adding device {45f8d680-1674-11e3-8008-444553540000} SWTOR Gaming Keyboard by Razer SWTOR Gaming Keyboard by Razer:1

[kissaki]

For me AudioOutput and AudioInput logs are followed by

 

2013-10-25 18:40:20.405 AudioInput: ECHO CANCELLER ACTIVE

2013-10-25 18:40:22.692 LogDocument::loadResource 2 "http://mumble.info/mumble.png"

2013-10-25 18:40:23.630 OpenSSL Support: 1 (OpenSSL 1.0.0k 5 Feb 2013)

2013-10-25 18:40:23.657 ServerHandler: QOS2 loaded

where the image is probably because of a snapshot install.

So maybe an OpenSSL / local certificate stuff issue.

You did wait more than a minute before killing the process, right?

For me the QoS part takes quite a bit of time on first launch.