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.
Shane Dixon commented
Hey I just installed the Beta https://www.displaylink.com/downloads/file?id=1552
And my odd display issue is fixed. All 3 Samsung and my laptop display are now working and the error log is gone!
Shane Dixon commented
I can verify this still is occurring on a 2020 16" Mac Pro latest Mac OS Update 10.15.4 with two display ports via a Startech dock and one HDMI to an apple usb-c to hdmi adaptor.
This is throwing that error almost 20 per second now.
My setup 3 Samsung C27F390 1080P monitors connected via HDMI to Display port and on HDMI to HDMI and if that third HDMI is plugged in I get an additional bug of a hard mirror between the HDMI and on (random) of the Display ports.
Martin Ayon commented
Same issue as everybody else in this thread. - I am running Catalina 10.15.3.
The "WIndowsServer" process is taking a 25% plus CPU impact, so pretty sure it's having a negative effect on the overall performance.
Are you guys fixing this anytime soon?
PS: I am using version 5.2. (59)
@Alban Rampon - Can you confirm if this is the DisplayLink macOS App PREVIEW - Beta 0.2 software?
If anyone is looking to stop the logging temporarily run the below command in Terminal:
sudo log config --process=$(pgrep WindowServer) --mode "level:off"
If you restart or shutdown your machine, it will have to be ran again. This was posted by @colliding with logic, in this forum post:
Writing this 30 times a second can't be right either. This is on Catalina, MacBook Pro 16, two Fujitsu 1920x1200 screens through a Think Pad dock.
Some exception is not handled right and it seems to cause quite an energy impact. Energy impact of >25. >10% CPU utilisation on a i9.
MacBook Pro (13-inch, Late 2016, Four Thunderbolt 3 Ports)
Driver 5.2.1 (that were provided for the model i'm using).
Running 1 Display with 1080p
Experiencing the same issue as Lee below. Does anyone know if there is any other DisplayLink Driver that is stable? Using macOS Mojave 10.14.6
Having the same issue. Have had about 20 crashes now with no Crash report from console only the message "bad magic"
I will lose both monitors for a few moments and then they come back about 30 or 40 times a day. so frustrating when your trying to work. My USB mouse is plugged in also but does not seem to be effected at all only the monitors.
Hoping that this can be fixed soon.................
+1 .WL-UG69PD2 with 4k monitors(viewsonic vp2768-4k) . I tried to use the corresponding driver between mojave(driver version 5.2) and catalina(driver version 5.2.1 release not bata), but there was still fps loss, it seems that it has not been resolved in 2020
+1 - DisplayLink just lags the whole Mac. Is there any alternative to display link?
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.
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!!!
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.
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?
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).
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?