You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If Mumble is running on a computer that has an analog input device (such as a Joystick, Racing pedals or similar), it will just completely freeze up or at least get very laggy.
CPU usage in such cases spikes as well.
Steps to reproduce
Start Mumble
Connect analog input device
Mumble version
1.4 and newer
Mumble component
Client
OS
Windows
Reproducible?
Yes
Additional information
It seems like this issue is more or less directly correlated to the switch towards RawInput on Windows (#6602). The assumed cause for the freeze is that the analog input device is just continuously generating input events, which Mumble receives and posts into the Qt event queue. However, the events are sent faster than Qt's event queue (and the respective handlers we have attached to it) can process. This leads to a congested event queue that in turn leads to a laggy application. Meanwhile the program is extremely busy discarding irrelevant input events, consuming a lot of CPU time while doing so.
Description
If Mumble is running on a computer that has an analog input device (such as a Joystick, Racing pedals or similar), it will just completely freeze up or at least get very laggy.
CPU usage in such cases spikes as well.
Steps to reproduce
Mumble version
1.4 and newer
Mumble component
Client
OS
Windows
Reproducible?
Yes
Additional information
It seems like this issue is more or less directly correlated to the switch towards
RawInput
on Windows (#6602). The assumed cause for the freeze is that the analog input device is just continuously generating input events, which Mumble receives and posts into the Qt event queue. However, the events are sent faster than Qt's event queue (and the respective handlers we have attached to it) can process. This leads to a congested event queue that in turn leads to a laggy application. Meanwhile the program is extremely busy discarding irrelevant input events, consuming a lot of CPU time while doing so.Related issues:
Also related:
Relevant log output
No response
Screenshots
No response
The text was updated successfully, but these errors were encountered: