Starting mumble will make computer go super slow a couple of seconds

[ElPumpo]

Whenever I start mumble my computer becomes really slow for 3-4sec. It has been like this for a long while, does it happen to anyone?

Running latest amd64 1.3.0 build, Windows 10 Insider Build 14342.

[mkrautz]

What happens is:

Mumble is using Windows hooks for global shortcuts. These are handled on the main thread.

Something during startup, presumably plugin auto-updates, cause the main thread to stall for 3-4 secs. The main loop is still running, but the Windows hooks aren't processed "fast enough".

This results in everything feeling laggy on the computer.

Note: It's possible that it's not just plugin updates, but something else as well.

[ElPumpo]

So, is fixing the issue going to happen?

[mkrautz]

Yep, milestoned 1.3.0.

[ElPumpo]

Btw here is a one year old log of Mumble usage. EDIT: ignore the spam of "QObject::connect: Cannot connect (null)::stateChanged(QNetworkSession::State) to QNetworkReplyHttpImpl::_q_networkSessionStateChanged(QNetworkSession::State)", it's my internet connection which fails.

[Tarun80]

I've noticed the same thing happens with Origin - it uses Qt Framework too - especially when updating. Not sure if this is of much help, but it could point to the cause?

[ibex-are-goats]

I still get this! (in mumble-1.3.0-1432-gf241782-snapshot.winx64.msi )

[ElPumpo]

Seens only to happen on the amd64 versions. . .

[ibex-are-goats]

The non-x64 build does something similar for me, as does 1.2 stable.

I'm pretty sure this defect has been around for a while. There are countless google hits for mumble mouse lag.

Is there a bounty we can donate to? I'd like to incentivize someone to fix this threading problem. Mumble is important software for the FOSS world and this defect needs to be fixed.

It's one thing to have a bug nobody sees. But a major usability defect on startup that every user sees for months or years is a major problem.

[Tarun80]

It only seems to happen on the first startup though. Any after that are fine. While it is an issue I wouldn't say it's really a "major" issue.

[ElPumpo]

It is if it turns users away from using mumble, basic logic.

[mkrautz]

@ibex-are-goats I don't think bounties will help. We don't have a system in place for bounties for the regular contributors. I can't say if posting to one of the bounty sites for FOSS will work, though!

The project itself takes donations at https://wiki.mumble.info/wiki/Donate. But they can't be earmarked to a particular feature.

[mkrautz]

Can you guys try something for me to help pinpoint this?

Try disabling winhooks:

https://mumble.info/reg/disable-winhooks.reg

and try using Mumble in that state. Does it work around this bug?

Once you're done testing, you can revert the change by re-enabling winhooks with:

https://mumble.info/reg/enable-winhooks.reg

Thanks.

[ElPumpo]

Yeah, that solves the issue.

[ibex-are-goats]

@Tarun80 To see how important this bug is, use me as your test subject: my last Mumble install date was 2014. I was going to migrate from Ventrilo. I took this bug as a sign of poor quality. Not to mention, my users would laugh at me for suggesting laggy software. I decided to delay migrating because of this bug. I then forgot about Mumble, and it took me 2 years to try it again now.

@mkrautz I'm guessing you are a lead developer? :) You may think of a quick workaround for this bug. But I am even more interested in supporting the long-term health of the Mumble project. Do you see a way that Mumble code can be refactored to be properly threaded, and thus prevent all related performance problems indefinitely? By "properly threaded" I mean "in a modern way", according to modern computer science practices, if you see what I mean.

If you see a solution to this problem that would help the project, I would like to donate directly to the people who you think could fix the problem. Or if you will not accept personal donations, I will donate to the project account.

[ElPumpo]

I can also refer to what ibex said, when I started to migrate from Skype to Mumble a lot of my friends went to TS3 after light usage of Mumble due to its hard initial mic setup. I'm still running Mumble for multiple reasons but I see the potential of this project, I don't see that in the projects' competitors.

The devs just needs BETTER feedback and people who accually report stuff.

[ibex-are-goats]

Well done, humans! We have conquered the unconquered and found our path to valhalla!

Because @mkrautz is so bashful, I will donate directly to the Mumble project. But my thanks go directly to you, good sir, for remedying our sore affections!

To infinity, and beyond!!!

[mkrautz]

Hold on. Better test the change first! I assume you haven't, since there isn't a snapshot available with the change in it? :)

[ibex-are-goats]

You can't change my mind!!! ;)

[ElPumpo]

ffs update amd64 snapshot 🎯

[mkrautz]

Hi,

Please test https://dl.mumble.info/mumble-1.3.0~1471~gac134d3~snapshot.winx64.msi and see if it's better with that snapshot.

It includes my "fix". Thanks.

[ElPumpo]

it does, finally! *thanks

[ibex-are-goats]

The fixed version works for me too!!! :) :+1:

@mkrautz I have noticed some suspicious mouse lag on my system which I want to report to you. I can create a new github issue if you think I should. Basically, I've been running mumble and murmur for a few hours, and I noticed my mouse lag at 3 random times while playing a game.

I am the only one connected to my server, and I am not transmitting. Normally I would think these mouse lags came from something going wrong with windows or a random app, but then I remembered I was testing mumble. So without having any way to log and identify what caused the mouse lag, I can only report what I've noticed, and my suspicion that it is mumble. This is on Win10 x64.

Let me know if you have heard of this before, or if I should create a new issue. I will of course try to reproduce the mouse lag I've noticed.