Unassigning, I'm not working on that one. Looking a bit to it I can confirm what Ken wrote, in some cases there is a low level event spam, seems like rather a kernel/udev/... issue, it just happens that u-s-s reacts to those events and the callback uses some cpu, so calling it in loop leads to the cpu usage
Unassigning, I'm not working on that one. Looking a bit to it I can confirm what Ken wrote, in some cases there is a low level event spam, seems like rather a kernel/udev/... issue, it just happens that u-s-s reacts to those events and the callback uses some cpu, so calling it in loop leads to the cpu usage