Fix the problem where DisplayLinkUserAgent eats 38% of my CPU
OS is windows 10, DLUA is 7.9.6.30.0. This often gets in a state where the user agent sets there using between 35 and 38% of CPU.
Neil MacMullen
shared this idea
7.9 M5 release for Windows is now available from our download area. Please create a support ticket for individual investigation if you meet any issue.
-
Mark Turner
commented
I am having the same issue, Win 10 Pro & DLUA 7.6.9.30. A few minutes post start-up it starts to consume a lot of CPU noticeable as the mouse becomes laggy. At the same time the Display driver seems to crash & recover?
Killing the task restores performance and no other ill effects. Leaving it for a while it calms down and has no noticeable other effects.
Good luck & hoping for a fix soon
-
Peter Kronenberg commented
The reason I asked about how necessary it is is that sometimes when it is using a lot of CPU, I go into Task Manager and just kill it. I don't seem to be losing any functionality by doing so.
-
The user agent in the user session is necessary and works with the service in session 0. Please be assured we would not go through the expense of developing something which you don't need.
I've assigned a high priority and our testing team is working on reproducing it now. Only when we have a reliable repro will our software engineers be able to properly address it. I will reach out to you if we need further information. If you create a technical support ticket, I will be able to tag it with the internal tracking number to notify you. -
I've been having the same problem. Just upgraded to 7.9.1336 (7.9M4) and still seeing the problem. Can you please explain exactly what DisplayLinkUserAgent does as opposed to DisplayLinkManager? Do we need it?
-
Neil MacMullen
commented
Thanks Alban - good to know it's a known issue and is being addressed