❔ Device Association, application runaway
I am making a C# .NET Framework 4.7.2 WPF application that communicates with some HID devices, and in the recent times have run into an issue with Device Association service spiking to very high CPU usage and thread count while my application is running.
It happens only on some machines as far as feedback suggests, and I personally cannot get to replicate the issue.
I am currently stumped as to where I could get information about what is causing said issue, since there seems to be no pattern to it other than the Device Association service itself. Are there any logs I could ask people to check, etc? It would be heavily appreciated if someone has some info on this.
8 Replies
If you need extra information, feel free to ask
can you quantify 'some'?
I'm not sure how many there are in total, since I'd imagine a lot of people don't care to write feedback about it, but I've had around 20 reports last week on different machines. They don't really seem to have any correlation between them other than using Windows 10 and Windows 11 (Which is to be mostly expected)
i meant how many "some devices"
Ahh, around 5 devices in total, though the issue appears even without any devices being plugged in or being communicated with
And by some HID devices I mean that we have HID device products, that all work with the same app, mostly though only one of them at a time
you know for sure one thing to check is what updates they have
or if you can identitfy at what point your application started giving this issue (like what commit)
starting with nothing in hand is pretty difficult
you could for example take an application to read events (not event viewer, one that read all the events) when the problems arises
maybe even read the system debug output (there should be a sysinternals tool to do that), but i don't think it would be that useful
if not then you shoul start testing pieces of your application to find the more likely culprit 🤷
Uff, currently in the process of doing exactly that, and asking them to try out some previous versions, very slow response wise unfortunately 😅
Thanks for the help though!
Was this issue resolved? If so, run
/close - otherwise I will mark this as stale and this post will be archived until there is new activity.