Random Mumble Client Freezes

[iggi-]

In and out of games I'm getting a weird freezing of the mumble program. The program locks up and the window turns grey like it is not responding. The overlay locks in the position it was when the program freezes. I can still hear others in the room normally, but the overlay does not light up their name. If I am talking when the program freezes, my mic is still open and everyone can hear what I am saying while the program is frozen and it does not release my mic until the program comes back from it's frozen state. This happens in and out of games, I can seem to find a correlation.

Windows dump file is located here (it was too large for github): http://www.mediafire.com/download/3cu2vr5ab04cv93/mumble.zip

The password was given to dD0T in IRC.

[Tarun80]

I too have been getting this issue recently. Prior to this it only occurred when Alt-Tabbed outside of games. I had reported the issue on the forums months ago. This issue just started with a recent snapshot. It was either http://mumble.info/snapshot/mumble-1.2.4-178-g2c892fe.msi or http://mumble.info/snapshot/mumble-1.2.4-184-g087e38a.msi that was the last snapshot that did not have an increase in freezes.

I suspect it's all related to the overlay, and that the issue I reported months ago was when the overlay code changes occurred to allow games like Guild Wars 2 to display the overlay.

[iggi-]

I will add I was using the snapshots up until this issue became apparent, at that point I reverted back to release 1.2.4. I'm still having issues on release 1.2.4

[hacst]

Don't have time to look into it right now but here the stacktrace and code the main thread was on in iggies dump:

Trace:

    [External Code] 
    QtCore4.dll!QThread::wait(unsigned long time=178625120) Line 552    C++
    [External Code] 
>   mumble.exe!OverlayClient::~OverlayClient() Line 95  C++
    QtCore4.dll!QObject::event(QEvent * e=0x0ad228f8) Line 1231 C++
    QtGui4.dll!QApplicationPrivate::notify_helper(QObject * receiver=0x09352688, QEvent * e=0x0ad228f8) Line 4555   C++
    QtGui4.dll!QApplication::notify(QObject * receiver=0x09352688, QEvent * e=0x0ad228f8) Line 4519 C++
    QtCore4.dll!QCoreApplication::notifyInternal(QObject * receiver=0x09352688, QEvent * event=0x0ad228f8) Line 928 C++
    QtCore4.dll!QCoreApplicationPrivate::sendPostedEvents(QObject * receiver=0x00000000, int event_type=0, QThreadData * data=0x00b48e90) Line 1555 C++
    QtCore4.dll!qt_internal_proc(HWND__ * hwnd=0x000303c4, unsigned int message=0, unsigned int wp=0, long lp=0) Line 496   C++
    [External Code] 
    QtCore4.dll!QEventDispatcherWin32::processEvents(QFlags<enum QEventLoop::ProcessEventsFlag> flags={...}) Line 810   C++
    QtGui4.dll!QGuiEventDispatcherWin32::processEvents(QFlags<enum QEventLoop::ProcessEventsFlag> flags={...}) Line 1204    C++
    QtCore4.dll!QEventLoop::exec(QFlags<enum QEventLoop::ProcessEventsFlag> flags={...}) Line 199   C++
    QtCore4.dll!QCoreApplication::exec() Line 1187  C++
    mumble.exe!main(int argc=1, char * * argv=0x00b0c998) Line 483  C++
    [External Code] 
    QtCore4.dll!qWinMain(HINSTANCE__ * instance=0x013b0000, HINSTANCE__ * prevInstance=0x0031f82c, char * cmdParam=0x01525b84, int cmdShow=1, int & argc=11577393, QVector<char *> & argv={...}) Line 191   C++
    mumble.exe!WinMain(HINSTANCE__ * instance=0x013b0000, HINSTANCE__ * prevInstance=0x00000000, char * __formal=0x0058379b, int cmdShow=1) Line 131    C++
    mumble.exe!__tmainCRTStartup() Line 547 C
    [External Code] 

Code in ::~OverlayClient:

OverlayClient::~OverlayClient() {
    delete qgpiFPS; // << Cursor pointed here
    delete qgpiTime;
    delete qgpiCursor;
    delete qgpiLogo;

    qlsSocket->disconnect();
    qlsSocket->abort();
    qlsSocket->deleteLater();

    ougUsers.reset();
}

[hacst]

@iggi- Oops. This completely slipped through the cracks. I forgot to assign and schedule it. We'll definitely take a look at this before 1.3.0.

@Langeh and @Tarun80 : To make sure you are actually experiencing this very issue and not something else a dump would be needed (you can grab one from the hanging mumble application using the task manager). If you decide to upload one make sure to password protect it though. As I told iggi these dumps probably contain your mumble certificate and/or passwords. I'm not interested in those but that's the way these full dumps work. Be aware that I might share the dump with other trustworthy core developers. You can mail the password to: dd0t (AT) users.sourceforge.net (if you want to encrypt it you can find my GPG key at http://mumble.info/gpg/dd0t.asc). Alternatively just privmsg it to me on IRC ;)

[Tarun80]

@dd0t: I've also been wondering if this is related to this issue reported back when the 1.2.4 snapshots first came to be?

It sounds a lot like the same thing that is occurring, so around the time of Aug 24, 2013. So between the 1.2.4 release and the snapshot of 1.2.4-139-g7c2d1a3 is when this issue may have truly started. I recall that in Guild Wars 2 the overlay didn't work in 1.2.4 and I've been using snapshots since.

[Tarun80]

@Kissaki, just to clarify, I would consider client freezing as Mumble Not Responding. Which is exactly what the original post references.

I mentioned the overlay because as I've reported both on the forums referenced above and recently here (as have others) that certain games - like Guild Wars 2 - will cause this issue (or one extremely similar to it) to occur. I've heard that it also happens with League of Legends too.

[Kissaki]

iggi- reporting this occuring out of issues makes it unlikely to be cause by the overlay.

When starting my self-compiled mumble client when DebugView is still running I reproducably have a hang-up of both. After some time it lifts. During this time, I can still use (some?) foreground windows, but can not switch Windows windows through the window bar or ALT+Tabbing.

[Juliaaan]

How do I make a dump of my mumble and send it?

[iggi-]

I have experienced it both in and out of league of legends.

[iggi-]

Also , this affects my brand new machine running 1.2.8. fresh-ish install of windows.

[Kissaki]

@Juliaaan what additional information to what we already have do you want to provide with that? What exactly do you mean by dump? Memory dump? Stack trace?

[Tritonio]

I'm having exactly the same problem for a year or so. Both on the desktop and in game. On Win7 64bit. Many versions up to 1.2.8.

[mkrautz]

Does your Mumble log (%APPDATA%\Mumble\Console.txt), contain any lines about dead overlay clients?

[mkrautz]

More specifically, something like:

Overlay: Dead client detected

[Tritonio]

Oh many times...

2014-09-26 13:41:46.010 SSL: CA certificate filter applied. Filtered size: 96, original size: 96 2014-09-26 13:41:46.012 ServerHandler: QOS2 loaded 2014-09-26 13:47:19.979 Overlay: Dead client detected 2014-09-26 16:09:53.373 Overlay: Dead client detected 2014-09-26 17:02:34.202 Overlay: Dead client detected 2014-09-26 17:30:53.757 Overlay: Dead client detected 2014-09-26 18:01:04.425 Overlay: Dead client detected 2014-09-26 18:59:29.220 Overlay: Dead client detected 2014-09-26 19:05:06.552 AudioInput: 40000 bits/s, 48000 hz, 480 sample 2014-09-26 19:05:06.553 WASAPIOutput: Latencies 100000 30000 => 100000 2014-09-26 19:05:06.553 WASAPIInput: Latencies 100000 30000 => 100000

[mkrautz]

Thanks.

Please try the latest snapshot build: http://mumble.info/snapshot/mumble-1.3.0~465~g78d7198~snapshot.msi

It blacklists Spotify, which caused the problem on my machine. Also, it contains better diagnostics for the issue, so in case the program causing the issue for you isn't Spotify, we can at least see the problematic program.

[Tarun80]

Adding mine in as well. With Guild Wars 2 this only happens when I'm alt-tabbed out of the game and actively talking on Mumble. Alt-tabbing back in when this happens causes it to unlock, or giving it a minute or two.

2014-11-17 12:19:22.276 Overlay: Dead client detected. PID 5024 "C:\Program Files (x86)\Guild Wars 2\Gw2.exe" 2014-11-17 12:24:58.018 Overlay: Dead client detected. PID 5024 "C:\Program Files (x86)\Guild Wars 2\Gw2.exe" 2014-11-17 19:11:41.644 Overlay: Dead client detected. PID 8768 "C:\Program Files (x86)\Guild Wars 2\Gw2.exe" 2014-11-17 19:26:08.985 Overlay: Dead client detected. PID 8768 "C:\Program Files (x86)\Guild Wars 2\Gw2.exe" 2014-11-17 22:48:12.194 Overlay: Dead client detected. PID 2500 "C:\Program Files (x86)\Guild Wars 2\Gw2.exe" 2014-11-17 22:59:23.228 Overlay: Dead client detected. PID 2500 "C:\Program Files (x86)\Guild Wars 2\Gw2.exe" 2014-11-18 01:40:24.274 Overlay: Dead client detected. PID 2500 "C:\Program Files (x86)\Guild Wars 2\Gw2.exe" 2014-11-18 03:28:50.138 Overlay: Dead client detected. PID 2500 "C:\Program Files (x86)\Guild Wars 2\Gw2.exe"

[Tritonio]

Got it too:

2014-11-19 14:27:22.640 Overlay: Dead client detected. PID 6644 "C:\Program Files (x86)\Webteh\BSPlayer\bsplayer.exe"

[Tritonio]

Got more:

2014-12-10 18:43:02.261 Overlay: Dead client detected. PID 7432 "C:\Program Files (x86)\AutoIt3\SciTE\SciTE.exe" EDIT: And more: 2014-12-09 16:49:43.257 Overlay: Dead client detected. PID 3044 "C:\Riot Games\League of Legends\RADS\projects\lol_air_client\releases\0.0.1.119\deploy\LolClient.exe"

[sandersaares]

I can confirm that adding Spotify to blacklist seems to have fixed the problem for me. It was occurring exclusively when Spotify was running.

[JoelTroch]

I'm not 100% sure about this, this issue could be connected to #1527, need more investigation.

UPDATE : I do have this issue but it is very rare, without the overlay and on Windows 7 x64 SP1

[DanielMarquard]

This has been happening to me for months on Windows 8.1 Enterprise x64 whether or not a game is open. Interesting to see that Spotify could be causing this, which I have open all the time. Testing that theory now.

[Tarun80]

Just to add information, Spotify is not installed on my machine.

[DanielMarquard]

Terminating Spotify seems to have fixed it for me. Hope you can get yours fixed, @Tarun80.

[Tarun80]

I had my entire computer lock up after a few days. Once I disabled the overlay the problem stopped completely.

[Kissaki]

Before someone else checks: Spotify was added to the default overlay blacklist in e5b6dac26dd317ca5115f78ef3ebc84aa7ca0a7b

[niwinz]

The same happens on linux version (1.2.19)

[ghost]

same here, random freezes, linux amd64 mumble 1.2.19, no overlay, no desktop environment.

[320x200]

same here.

random freezes of the GUI, Debian Sid, Mumble 1.3.0~git20190125.440b173+dfsg-2, no overlay, just evilwm, gajim and firefox running.

[ghost]

Since moving from Qt 4 to Qt 5, is this an issue anymore?

[github-actions[bot]]

This issue has been marked as stale, because our request for more information has thus far not been fulfilled.

If no further action occurs, this issue will be closed within 7 days.

[320x200]

following up my last comment (from 2019), I haven't experienced a problem in a long while (mumble is now 1.3.4 on sid). So I guess something at some point got fixed somewhere, and I'm very grateful for it :)

[Krzmbrzl]

Great! Thanks for letting us know :)