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
Hello there,
I came accross an issue while using HidSharp 2.1.0 on Linux raspberrypi 5.10.17-v7l+.
I am using an USB device that be rebooted via a HID message. I send in the command, receive an acknowledgment and then the device reboots and the connection is lost.
The HidSharp API is behaving fine and the connection loss is handled perfectly.
However I noticed that a background thread was using 100% CPU after sending the command and after investigation, I found that the thread was stuck in an infinite loop in LinuxHidManager.Run:
The call to NativeMethods.poll() always returns revents=0 and thus we never exit the while loop.
The commented code is mine and is my naive attempt at fixing the problem. The fix works, but I'm pretty sure I'm missing something in the big picture.
Please tell me if I can provide any more useful information.
With regards
Victor
The text was updated successfully, but these errors were encountered:
Hello there,
I came accross an issue while using HidSharp 2.1.0 on Linux raspberrypi 5.10.17-v7l+.
I am using an USB device that be rebooted via a HID message. I send in the command, receive an acknowledgment and then the device reboots and the connection is lost.
The HidSharp API is behaving fine and the connection loss is handled perfectly.
However I noticed that a background thread was using 100% CPU after sending the command and after investigation, I found that the thread was stuck in an infinite loop in LinuxHidManager.Run:
The call to NativeMethods.poll() always returns revents=0 and thus we never exit the while loop.
The commented code is mine and is my naive attempt at fixing the problem. The fix works, but I'm pretty sure I'm missing something in the big picture.
Please tell me if I can provide any more useful information.
With regards
Victor
The text was updated successfully, but these errors were encountered: