Murmur Timeout Log Spam

[nacey]

This is sort of a carry-over from my previous thread but it's not directly related as that issue is resolved. So I decided to make a new thread for it.

This isn't causing me any visible issues as far as I can tell, but it would be nice if the log didn't get spammed so much and maybe one of the devs would be interested in looking at this. But please, consider it low priority as far as I am concerned.

What happens is I get a whole bunch of timeout messaages spamming my log, once every 15.5 seconds. It doesn't happen all the time though. So I traced through the log and found the start point, this:

<W>2010-12-21 14:43:48.250 1 => Not registering server as public
<W>2010-12-21 14:43:49.296 1 => <1:(-1)> New connection: 79.x.232.224:49873
<W>2010-12-21 14:43:49.562 1 => <2:(-1)> New connection: 109.x.141.246:49567
<W>2010-12-21 14:43:49.750 1 => <1:(-1)> Client version 1.2.2 (Win: 1.2.2)
<W>2010-12-21 14:43:50.140 1 => Starting voice thread
<W>2010-12-21 14:43:50.203 1 => CELT codec switch ffffffff8000000b 0 (prefer ffffffff8000000b)
<W>2010-12-21 14:43:51.125 1 => <1:Commisar(26)> Authenticated
<W>2010-12-21 14:43:51.265 1 => <3:(-1)> New connection: 93.x.156.137:51409
<W>2010-12-21 14:43:51.437 1 => <4:(-1)> New connection: 93.x.156.137:51436
<W>2010-12-21 14:43:51.671 1 => <2:(-1)> Client version 1.2.2 (Win: 1.2.2)
<W>2010-12-21 14:43:52.750 1 => <2:NATO(21)> Authenticated
<W>2010-12-21 14:43:53.953 1 => <5:(-1)> New connection: 94.x.96.191:53045
<W>2010-12-21 14:43:54.234 1 => <5:(-1)> Client version 1.2.3 (Win: 1.2.3-rc1-8-g979bf30)
<W>2010-12-21 14:43:54.515 1 => <5:Cowbie(20)> Authenticated
<W>2010-12-21 14:43:54.750 1 => <4:(-1)> Client version 1.2.2 (Win: 1.2.2)
<W>2010-12-21 14:43:55.718 1 => <4:Tom(13)> Authenticated
<W>2010-12-21 14:44:21.140 1 => <3:(-1)> Timeout
<W>2010-12-21 14:44:36.656 1 => <3:(-1)> Timeout
<W>2010-12-21 14:44:52.156 1 => <3:(-1)> Timeout
<W>2010-12-21 14:45:07.656 1 => <3:(-1)> Timeout
<W>2010-12-21 14:45:23.421 1 => <3:(-1)> Timeout
<W>2010-12-21 14:45:38.734 1 => <3:(-1)> Timeout
<W>2010-12-21 14:45:55.437 1 => <3:(-1)> Timeout
<W>2010-12-21 14:46:10.015 1 => <3:(-1)> Timeout
<W>2010-12-21 14:46:25.187 1 => <3:(-1)> Timeout
[etc.]

It seems as though one of the clients ("Tom") is attempting to connect twice, and the first connection is being lost. So then it keeps causing a timeout. The interesting thing is that it is always the same user who is causing it. I will get him to reinstall Mumble for a start.

Let me know if I can do anything else or provide more info.

Thanks.

[pcgod]

You could try the test build which I posted in the other thread. It has the patch which could fix that but I don't know if it really does.

[nacey]

Ah, sorry, I thought that was just for the time skip issue. Will give it a whirl and report back, thanks :) .