Fix "WindowServer [ERROR] - Unable to find display pipe for IOFB service: 18715" on MacOS
DisplayLink do not work properly with 4K screens @ MacOS 10.14. It looks laggy, jamming, like FPS drop.
I've described issue in details here: https://displaylink.org/forum/showthread.php?t=66349
The new driver architecture, currently in beta, is confirmed not to prompt this log entry.
-
Anonymous commented
+1 - DisplayLink just lags the whole Mac. Is there any alternative to display link?
-
bob commented
you mean this isnt the reason that there is a memory leak in the windows server?, and it eats up all my memory
-
Amitabh Mehta commented
🎂
We've past one year anniversary of this issue.
If you can do nothing else, please stop logging this message. -
Zev Green commented
My machine just crashes after a while, or by using Google Meet when connected to the targus displaylink box. I'm running the latest beta and submitted reports using the tool.
-
AB commented
Upgraded to Catalina 10.15.1 and also seeing this message bombard my console
[ERROR] - Unable to find display pipe for IOFB service / regID: 0x4b03 / 0x100000532
Around 20 per second!!!
-
Matt commented
Can anyone recommend an alternative USB-C/Thunderbolt3 adaptor for Macs that doesn't need the DisplayLink driver, but can still support dual digital displays? With this and the constantly high CPU use, I'd rather ditch the Dell adaptors we've bought and switch to something else.
-
Matt commented
I am having this same issue, on Mojave 10.14.6, having held off from updating to Catalina, solely awaiting DisplayLink to update their driver.
Trying to diagnose another issue is pretty much impossible thanks to Console filling up with "[ERROR] - Unable to find display pipe for IOFB service".
DisplayLink people: surely it's easy to supress this? -
Steve commented
I concur with Catalina about the existence of the Error logs, however I think the overall performance is better in Catalina than Mojave - After upgrading to Catalina I had to install the Beta DisplayLink drivers (5.2.1 Beta 2) since the Mojave 5.2 drivers did not work (displayed a cursor but never any windows). I only saw the spurious Console errors whilst debugging something else, if nothing else these errors clutter the console making it difficult to debug other stuff
-
Edward Benyukhis commented
It continues to happen with MacOS Catalina (10.15).
-
Sunshine commented
Hello
Same issue here, do you have a solution for it? It has already been a long time, how can it be that you guys not are able to provide a solution?
-
tom commented
Well every day with 50. to 5.2 drivers the Windows Server on my 10.14.6 Mac gies absolutely insane in CPU utilisation driving the fans to turn on. The WindowServer remains high CPU process at 35% when the monitors are disconnected. You need to reboot twice to reduce the window server utilisation. Without using DisplayLink every thing runs fine. To myself it would appear that the continuous error over 6-8hrs drives some thing to break in the window server itself. https://www.displaylink.org/forum/showthread.php?t=64931&page=2
-
Diego commented
I have thousands of this too. MacBook Pro 15 2019, Dock Dell D3100, two Dell P2419H (fullhd). Latest macOS and DisplayLink.
-
Mike McGinley commented
Just curious... is anything being done to address this issue? Myself and about 10 other developers I know have the exact same issue. Running Mojave 10.14.3 and DOCK180USZ-52.
I was becoming more and more frustrated at the incredibly poor performance of my mac when connected to the Targus. After starting down the rabbit hole (like you all seem to have done), I wound up here. After a day or two of connecting, disconnecting, etc, the macbook's primary display will suddenly go black... and never comes back. I have to hold the power button down every time to get the display back up.
This is really frustrating as the only way to take advantage of the attached 4k monitors is through the (seemingly) buggy DisplayLink software.
Everyone in my office tested the process of uninstalling Display Link and it fixes the issue every time - but at the loss of 4k video and Ethernet/peripheral connectivity.
-
Anonymous commented
@Wim thanks for your response after half a year! I'd like to believe it's because your busy with fixing issue.
-
Erik commented
And none of my connected monitors is running 4K.
Most reproducible error: trying to attach a file to an email in Outlook 365. The choose file window cannot spawn, beach ball ensues, and Outlook must be force quit. Removing DisplayLink fixes all of this. Console message described in OP is running like wildfire in Errors.
-
Erik commented
Same here. 2016 MacBook pro is unusable with 5.1.1 drivers installed on MacOS 10.14.4.. It cannot spawn windows for many applications, resulted in frequent hangs. Had to uninstall.
-
Aleksandar commented
Same here.
Macbook Pro Mid 2014
OS X: 10.14.4
The dock is a Targus Universal DV4K
Display Link driver: 5.1.1 -
anonymous commented
same here. macbook pro '16, mojave 10.14.4, thinkpad 40ac dock
-
Hami commented
I have the same issue, found the same error log in console.app.
I'm using lenovo dock 40AF0135CN, Macbook Pro 13" (2018), connecting a 4K monitor.
It's laggy and having FPS drop when using resolution "1920 x 1080" (which displays in retina mode).I have to workaround by using 1080p (which displays in 2K mode, blurry and wasted my 4K monitor) but at least it allows me to continue using it.
Hope the next update on the driver will address this issue.
Thanks! -
Fred commented
Same issue with my Macbook Pro 15", running driver 5.1.32 and Mojave 10.14.3.
My dock is WL-UG69PD1.