Fix the problem where DisplayLinkUserAgent eats 38% of my CPU
OS is windows 10, DLUA is 126.96.36.199.0. This often gets in a state where the user agent sets there using between 35 and 38% of CPU.
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.
Basil Buwalda commented
I have the same issue with my MS Surface Pro 3 - Can I please have “Dev Build for 21156" or a link to where I can create an issue from please.
Anonymous: I don't see how I can share a file with "anonymous". Please create a support ticket so we have your email address and so we can follow-up with you individually.
Arash: 7.9M5 is anticipated for the second half of February. The exact date will depend on how the testing progresses. I prefer delaying to knowingly release something not satisfactory!
Waiting for the release is a good idea if not too annoyed as development builds aren't fully tested and can bring collateral damage. That's why we do individual follow-ups. I will update the status of this suggestion when the driver is released. Therefore, if you have subscribed for email updates, you'll be notified. Alternatively, you can create a support ticket asking to be notified when 21156 is fixed.
I am experiencing this issue as well on my macbook air. Could you please send me the Dev Build for 21156 as well? Thanks
Experiencing similar issue. It seems to occur after the computer wakes up from sleep. When do you anticipate to release a new official driver? And what are driver update instructions? I'd like to wait for the official release to update.
I have the same Issue (high CPU load, freezing graphics, hangin INTEL HD graphics) on my DELL XPS and need “Dev Build for 21156” to try/install.
Mike Johnson commented
Like Hugh below, I don't see where you can create a "support ticket" on your support website. I would also love to test "Dev Build for 21156" as I get this problem quite often!
After 2 business days of heavy usage, I can attest that the dev build resolved the issue on my laptop (both the high CPU usage and the crashing Intel Display Driver).
One happy camper
Rolling back to a system restore from yesterday has fixed the issue...
I'm not sure where to create the support ticket but can you make the Dev build available to me? Since I opened my computer today the monitor resolution was set to the minimum and DisplayLinkUserAgent is using 10% of CPU with constant high fan noise. Looking at the resource monitor I can see the DisplayLinkManager is using an average of 26% of my CPU all the time
I've got the same issue with my Surface Pro 3 ever since I upgraded to Win10 x64.
And just as Lee Eyre reported I get the message that the intel graphics driver stopped responding - never had that using Win8.1 or on Win10 before installing DL-drivers
This has been occurring with my Toshiba U3 (DisplayLink) docking station since M4 release on Win10 x64 on an XPS 9530. Seems like huge regression.
I have similar U3 at home and in the office and both have same issue.
Also, Intel Display driver crashes every so often. Setting Office to "Disable hardare acceleration" makes things slightly better.
Tom Antonovich commented
This has been occurring with my Dell (DisplayLink) docking station for months now on Win10 x64 on an XPS 9530. I'm really frustrated that there is still no fix for this...
Jim Martin commented
Good to see this is already reported. I am also experiencing the same issues on Windows 10 64-bit with the latest DL drivers. Would love to be notified when a resolution is reached. It is odd that killing the Display Link User Agent appears to have no impact on my system other than to release the CPU usage.
Lee Eyre commented
I also have the same issue and in addition regularly have my screen freeze followed by a message that the intel graphics driver stopped responding, not sure if the problems are related. Running a Surface Pro 3 with a 4K monitor attached.
Win 10 64bit Pro (with latest updates) on i7-5500U 8GB RAM Ultrabook, Intel HD Graphics 5500 + NVIDIA GF840M 2GB and DisplayLink Manager version 7.9.1336.0.
In my case most CPU % use is by "DisplayLinkManager Application" where over 10% is used even when text scrolling business application is run. "DisplayLinkUserAgent Application" uses about 2%. Together consumes over 12%. Excess fan noise of Ultrabook and slowdown of vital applications due to this prevents me from using the DisplayLink dock that cost me around USD100 and still have to plug extra HDMI cable to use external monitor.
So please provide a fix soon. No point people spending money on these docks otherwise.
Same problem here: Win10 (up to date) and DisplayLink active.
Sometimes without any special action on my side the DLUA starts to eat up 30% of CPU time.
As Mark noted this coincides with a very short disruption of the DL video adapter (2nd screen blanks and recovers within a second).
I also "solve" this by killing the DLUA process without any loss of functionality (that I would notice, that is).
Unfortunatley I have seen the DLUA run amok even w/o any DL adapter attached. When this happens it will drain the battery of a notebook (Surface 2 Pro) real fast :/
Mark Turner commented
I am having the same issue, Win 10 Pro & DLUA 188.8.131.52. 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.
Peter Kronenberg commented
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?