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.
-
Miquel commented
Please, someone could explain why is this happening and why there isn't a working update. Today, at 2021/08 with a new installation (10.4.6 Mojave Os) and recent driver v5.2.5 and tested with 2 apple Display 21' on a MBPmid2012. I supose you give support to Mojave OS, then please give a solution. Thank you
-
Ortho Black commented
Still getting this error with the latest drivers, is anyone working it?
-
Justin Stewart commented
Still getting this error with 10.15.7 and latest driver 5.2 installed, screen recording enabled, no blocked extensions.
-
Anonymous commented
> The new driver architecture, currently in beta, is confirmed not to prompt this log entry.
Does not work in 10.14 Mojave; installer requires 10.15 Catalina
-
gambo commented
Is there a beta driver available for this error ? I am seeing these messages in my logs constantly. On latest Catalina 10.15.5 and latest drivers 5.2.4.
-
CB commented
I am having this same issue, however, I'm not running anything external 4k - one old Apple 21" Cinema Display (dvi) and an old Toshiba television (HDMI), both running off my MacBook Pro 2017 TB.
But this error is spamming Console - I have over 148,000 error messages in the past 15 minutes.
I'm on Mojave. I downloaded the new driver in March.
-
Andrew commented
> The new driver architecture, currently in beta, is confirmed not to prompt this log entry.
This is true — but only because the Beta PREVIEW DisplayLinkDriver does not work at all on Catalina 10.15.4. Kernel Extension is loaded and enabled but Displaylink does not show up in Security & Privacy Settings, and Displaylink monitor is black.
Uninstalling and going back to the released driver lets the monitor work again, but with hundreds of these messages per second.
-
Robert commented
Will there be a fix for 10.14.x for those of us stuck on Mojave?
-
Ian Davies commented
When is the beta driver which contains this fix likely to be released?
-
Garry commented
Thanks, this was working ok for me well enough until the last Catalina update (MacBook Pro 2018) and then suddenly we were having the reboot overnight or whenever I walked away for more than an hour thing going on. Now this new beta driver seems to have solved it. Or at least I don't get the massive spew of messages to the logs, overnight still to be tested but I imagine that was it. And this is with the beta 0.5.25 driver and OS 10.15.4.
-
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.
Very unstable...
-
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)
-
Alex commented
@Alban Rampon - Can you confirm if this is the DisplayLink macOS App PREVIEW - Beta 0.2 software?
-
Alex commented
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:
https://www.displaylink.org/forum/showthread.php?p=89342&posted=1#post89342 -
js commented
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.
-
Anonymous commented
Same here
I'm on:
MacBook Pro (13-inch, Late 2016, Four Thunderbolt 3 Ports)
10.15
Driver 5.2.1 (that were provided for the model i'm using).
Running 1 Display with 1080p -
Alex commented
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
-
Lee commented
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.................
-
tianen commented
+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