![]() ![]() Without DisplayLink installed and at 17:39:26 each day the WindowServer process goes high CPU to approximately 40% and remains there until 18:10. ![]() I've trashed Mojave again and reinstalled office and a few minor other applications. You can try swapping Users when it happens I found that this causes it to go away.or 2 reboots seems to fix it as well (often 1 reboot does nothing).īest of luck don t see this ever getting fixed.Catalina I think will be an experience an a half for Displaylink. Short answer is not much you can do about it as it would appear its a displaylink problem and maybe only with 14.6. I meant to actually save a log to send to support today when it occurred but unfortunately I also need to work. I notice because I work in a quite environment and I hear the fans go off I can almost guarantee what is happening. So, I guess the answer is it is not just you on 14.6 that has this problem but there are a number of us that have noticed there PC go insane with displaylink drivers. I stay away fro driver 5.2 because when I use that and its not connected to a display link dock external thunderbolt monitors do not work. This happens on driver version 5.0, 5.1 and 5.1.1. Sure enough after about 10hrs I get 150% for DisplayLink and another 35% for window driver CPU utilisation. Nothing else installed except Mojave and Displaylink. Thinking it was some hing else I had loaded I took the trouble on the weekend to do a complete backup and reinstall of Mojave. I get the same problems every single day. I have a 2017 4 USB-C port MAC and my work forces me to use a Dell 3100 dock. Is there any fix for this? I have recently bought this DisplayLink device and am quite disappointed by the CPU hogging that is occurring. Your developers will be able to repeat this very easily by doing the above!!! It seems that the entire screen is being polled to be pushed out to the external DisplayLink hardware, without any form of acceleration. Nothing of note comes up in that other than some secondary thread is very very busy, but as it is not a debug build I cannot see what it is actually doing. I also tried running Instruments and looking at DisplayLinkManager. I tried running Quartz Debug to see when screen updates were occurring but this irritatingly doesn't work over DisplayLink, so I have no idea whether the Screen Sharing is refreshing its view far too often (I am using adaptive quality, not full), causing DisplayLinkManager to try and push these updates through to the WindowServer, causing a global system slow down. I have looked at Activity Monitor to see that, in this order, the following are consuming CPU:ĭisplayLinkManager and Screen Sharing are hogging about the same amount of CPU. If the other machine is doing frequent updates (eg like some redrawing of part of a webpage, a very common occurence), then the CPU will go insane on my Mac. This is repeatable on my MacBook Pro 2012 using Mac Screen Sharing to VNC to another machine. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |