Murmur crashes my Mumble

[eliittihemuli]

When my murmur is on, I can join there for a few seconds with mumble, but then it crashes. It only crashes when I have murmur on. When I join my friends murmur server without having my murmur on, my mumble works fine without crashing. I've tried that and some other things to see what causes it to crash. Couldn't find any other reason for it crashing than having both murmur and mumble enabled at the same time. Anyone knows why this happens?

[kissaki]

No. No idea. Should not happen.

Can you provide some debug/log information?

Did you send a crash dump upon crash?

[eliittihemuli]

Very strange and irritating, now it works fine as I'm on my Murmur with my friends, sometimes Mumble just crashes and sometimes don't... I'll post the crash information next time it happens.

EDIT: Alright so it started to happen once again, guess it was a temporary when it worked for the one time. I do send crash reports every time it crashes, but where I can find the crash log so I could post it here?

EDIT 2: Found them, obviously on the Murmur log of course, posting them on a new post as a thread bump.

[eliittihemuli]

2012-10-05 19:56:50.595 Initializing settings from C:/Program Files (x86)/Mumble/murmur.ini (basepath C:/Program Files (x86)/Mumble)

2012-10-05 19:56:50.609 OpenSSL: OpenSSL 1.0.0c 2 Dec 2010

2012-10-05 19:56:50.611 SSL: Adding recommended CA AAA Certificate Services

2012-10-05 19:56:50.611 SSL: Adding recommended CA UTN-USERFirst-Client Authentication and Email

2012-10-05 19:56:50.624 ServerDB: Openend SQLite database C:/Program Files (x86)/Mumble/murmur.sqlite

2012-10-05 19:56:50.709 MurmurIce: Endpoint "tcp -h 127.0.0.1 -p 6502" running

2012-10-05 19:56:50.710 Murmur 1.2.3 (1.2.3) running on Win: 6.1.7601.1: Booting servers

2012-10-05 19:56:50.862 1 => Server listening on [::]:64738

2012-10-05 19:56:50.987 1 => Server listening on 0.0.0.0:64738

2012-10-05 19:56:51.070 1 => Announcing server via bonjour

2012-10-05 19:56:51.132 1 => Not registering server as public

2012-10-05 19:57:00.950 1 => <1:(-1)> New connection: [fe80::d5f4:29c9:44a6:6d7b]:53004

2012-10-05 19:57:00.951 Connection: Failed to add flow to QOS

2012-10-05 19:57:01.153 1 => <1:(-1)> Client version 1.2.3 (Win: 1.2.3)

2012-10-05 19:57:01.245 1 => Starting voice thread

2012-10-05 19:57:01.327 1 => CELT codec switch ffffffff80000010 0 (prefer ffffffff80000010)

2012-10-05 19:57:01.412 1 => <1:Eliittihemuli(-1)> Authenticated

2012-10-05 19:57:39.653 1 => <1:Eliittihemuli(-1)> Connection closed: The remote host closed the connection [1]

2012-10-05 19:57:39.728 1 => Ending voice thread

2012-10-05 20:01:56.630 1 => <2:(-1)> New connection: [fe80::d5f4:29c9:44a6:6d7b]:53136

2012-10-05 20:01:56.631 Connection: Failed to add flow to QOS

2012-10-05 20:01:56.781 1 => <2:(-1)> Client version 1.2.3 (Win: 1.2.3)

2012-10-05 20:01:56.929 1 => Starting voice thread

2012-10-05 20:01:57.014 1 => <2:Eliittihemuli(-1)> Authenticated

2012-10-05 20:02:32.421 1 => <2:Eliittihemuli(-1)> Connection closed: The remote host closed the connection [1]

2012-10-05 20:02:32.608 1 => Ending voice thread

Shows two of my crashes, was alone this time though but apparently it doesn't matter. Oh right, by the way, we use Hamachi and LAN settings as we haven't done anykind of port forwarding. This isn't the problem though as it works with my friend.

[kissaki]

That only provides the server log. It only shows your client loses the connection.

Maybe you could get Debugview http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx

and see if it provides any useful information!?

[eliittihemuli]

That only provides the server log. It only shows your client loses the connection.

Maybe you could get Debugview http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx

and see if it provides any useful information!?

 

Sorry for my late response. So I tried the Debugview, couldn't understand much of it but it did something when Mumble crashed. Crash occurs in row 39. Here it is:

http://imageshack.us/a/img221/8664/nimetnv.png

http://imageshack.us/a/img221/8664/nimetnv.png

EDIT: I don't know much about those but does the WASAPI have anything to do with the crash? "Disabled as WASAPI is available"

[kissaki]

WASAPI is the Windows (>Vista) sound API. As it is available on your system, the less-feature-richt/older DirectSound is not used, thus disabled. No problem there.

The unknown opcodes shouldn’t cause a crash neither - at least they did not for me some time ago.

Also, they should not make Mumble crash but the application the Overlay is injected into, if at all (HardHook is the injection mechanism).

Furthermore, the debug message “Overlay listening on” follows, further indicating this was not a problem (that crashed).

Everything listed on the screenshot seems ok, and still be initialization, thus before the crash.

What follows?

Also, which OS are you on and which Mumble version are you using?

[eliittihemuli]

WASAPI is the Windows (>Vista) sound API. As it is available on your system, the less-feature-richt/older DirectSound is not used, thus disabled. No problem there.

The unknown opcodes shouldn’t cause a crash neither - at least they did not for me some time ago.

Also, they should not make Mumble crash but the application the Overlay is injected into, if at all (HardHook is the injection mechanism).

Furthermore, the debug message “Overlay listening on” follows, further indicating this was not a problem (that crashed).

Everything listed on the screenshot seems ok, and still be initialization, thus before the crash.

What follows?

Also, which OS are you on and which Mumble version are you using?

 

Mumble version 1.2.3

Murmur also 1.2.3

Windows 7 Home Premium 64-bit

I really have no idea what causes the Mumble to crash, but I know that so far it only crashes when I join my own Murmur server as it doesn't crash when I join my friends Murmur while also having my Murmur on.

[kissaki]

Everything listed on the screenshot seems ok, and still be initialization, thus before the crash.

What follows?

[eliittihemuli]

Everything listed on the screenshot seems ok, and still be initialization, thus before the crash.

What follows?

What do you mean what follows? Nothing, it just crashes and that's that. Here is another picture showing only me connecting to my Murmur and the Mumble crashing.

http://imageshack.us/a/img703/811/nimetnco.png

http://imageshack.us/a/img703/811/nimetnco.png

Row 1 connection

Row 9 end of crash and nothing "follows"

[kissaki]

Oh, ok.

Given your log screenshot above, further log messages followed line 39 not even a second afterwards, indicating that line was not actually the crash/at least things followed.

Hm. The overlay really should not be dependant on what server you connect to in any way though.

Could you try disabling the overlay in Mumbles settings, and see if that helps?

The hard-hook should not be effective then, thus that line never appear.

[eliittihemuli]

Oh, ok.

Given your log screenshot above, further log messages followed line 39 not even a second afterwards, indicating that line was not actually the crash/at least things followed.

Hm. The overlay really should not be dependant on what server you connect to in any way though.

Could you try disabling the overlay in Mumbles settings, and see if that helps?

The hard-hook should not be effective then, thus that line never appear.

 

Disabling the overlay was one of the first things I tried to do, unfortunately it doesn't work.

I do have another theory why it crashes, opening it with administrator settings doesn't work, disabling and enabling this and that doesn't work, but I noticed that it crashes only the two the first times and then it works, but if I change the settings or disconnect a channel, then it crashes two times again but after that it works, again until I change something.

I'm serious, it crashes the first two times and then it works, and if I change something, almost anything, it crashes two times again.

And still Mumble crashes when Murmur is on, there is something somewhere, but it's pretty hard to find it as I have no idea where. :?

[kissaki]

When it crashes with the overlay disabled, what does the debug log say?

It certainly should not display the hooking unknown opcodes anymore.

[eliittihemuli]

Will post the log when I next time use Mumble, might take some time.

[hacst]

This sounds unusual so some into the blue guessing:

Are the crashes limited to mumble or do you experience problems with other applications too?

Are the drivers on your system up to date (especially network and sound)?

Does switching off "Quality Of Service" in Mumble's configuration change anything?

The client also writes a log that might contain useful information. You can find it under %APPDATA%\Mumble\ . It's called Console.txt . I would like to take a look at the crash dumps you uploaded. To find it amongst the others I'd need the following information (or at least most of it ;) ): Comment you set, Email you set (make sure to obfuscate it someway or something), Date of upload and your exact mumble version (as displayed in Mumble's about dialog).

Hopefully we can get to the bottom of this.

[eliittihemuli]

I really apologise for my very late response, I took a little break on gaming.

Here is the debug view with overlay disabled.

http://img560.imageshack.us/img560/4109/nimetnoa.png

http://img560.imageshack.us/img560/4109/nimetnoa.png

And according to dd0t, here are the last console.txt rows on appdata. (I wasn't sure should I upload the whole .txt somewhere or just a picture of it, I can upload logs and things for you people if you need to have a look at them.)

http://img28.imageshack.us/img28/5364/nimetncc.png

http://img28.imageshack.us/img28/5364/nimetncc.png

Are the crashes limited to mumble or do you experience problems with other applications too?

Mumble is the only thing that crashes when Murmur is active.

Are the drivers on your system up to date (especially network and sound)?

Yes, they are, I keep everything on my PC up to date.

Does switching off "Quality Of Service" in Mumble's configuration change anything?

Mumble didn't crash when I disabled Quality of Service, frankly this could have only been a coincidence as Mumble sometimes doesn't crash at all, rarely though.

Mumble version 1.2.3

Murmur version 1.2.3

[kissaki]

If it does not crash with QoS disabled, your issue is very probably broken network drivers which can not handle QoS.

[eliittihemuli]

So what can I do for it? Do I need to update my network drivers?

With all due respect, for myself this issue doesn't matter that much, I can still use Mumble to voice-chat with my friends. And because of that I'd like to just leave this matter here.

But for the greater good, I still can continue trying to figure out this problem.

Please let me know which one should we do.

[kissaki]

Just leave QoS disabled.