Steps to Reproduce
Mute/unmute really fast, or switch channel 7/8 times quickly.
Expected behavior
switching mute mode should work, and all channel switch should be issued correctly.
Describe the bug
After investigating for quite some time, I could not identify where the issue could come from.
When a user joins a channel on the mumble 1.3.2 compiled for debian stretch, it seems that switching channel or muting/unmuting (basically any command operation) drops after a while.
For instance, if a user joins the channel, and switches channel quite fast, at one point his channel switch will be dropped. This becomes more of an issue when it comes to muting/unmuting. If you mute/unmute too fast a few times in a row, you'll be stuck and cannot change the mode for a while.
From my point of view it could be something related to burst messaging on the control channel. I tried setting burst_message and limitmessage to a high value (65536) without effect. I also thought it was because of the low I/O of the server, so I put the database in a ramfs. I also tried on public server, where similar behaviour can be observed.
Also I thought it could be related to a client issue, so I tried on linux, windows and plumble-free on Android, which show the same behaviour.
The issue seems to be deterministic as if I switch too fast channel 7/8 times in a row, the following switch of channel will not be issued. (Tested on various public servers)
Versions
Various server versions, up to 1.3.2 self-built on debian stretch
Various client version (linux/Windows/Android) in version 1.3.2
Steps to Reproduce Mute/unmute really fast, or switch channel 7/8 times quickly.
Expected behavior switching mute mode should work, and all channel switch should be issued correctly.
Describe the bug
After investigating for quite some time, I could not identify where the issue could come from. When a user joins a channel on the mumble 1.3.2 compiled for debian stretch, it seems that switching channel or muting/unmuting (basically any command operation) drops after a while. For instance, if a user joins the channel, and switches channel quite fast, at one point his channel switch will be dropped. This becomes more of an issue when it comes to muting/unmuting. If you mute/unmute too fast a few times in a row, you'll be stuck and cannot change the mode for a while.
From my point of view it could be something related to burst messaging on the control channel. I tried setting burst_message and limitmessage to a high value (65536) without effect. I also thought it was because of the low I/O of the server, so I put the database in a ramfs. I also tried on public server, where similar behaviour can be observed.
Also I thought it could be related to a client issue, so I tried on linux, windows and plumble-free on Android, which show the same behaviour.
The issue seems to be deterministic as if I switch too fast channel 7/8 times in a row, the following switch of channel will not be issued. (Tested on various public servers)
Versions
Additional context
A similar issue has been reported earlier this year : https://github.com/mumble-voip/mumble/issues/3985