Endless log spam _CGXGLDisplayContextForDisplayDevice: No matching context for device

[duncanm]

As a temporary fix you can enter the following in your terminal:

sudo log config --process=[PID] --mode "level:off"

where [PID] is the ID of the process you see in the console.

You have to re-do it every time you re-start your mac which is a pain, but at least it saves all those writes to your disk

[wa2flq]

That works, thanks.

[dude123]

Originally Posted by duncanm

As a temporary fix you can enter the following in your terminal:

sudo log config --process=[PID] --mode "level:off"

where [PID] is the ID of the process you see in the console.

You have to re-do it every time you re-start your mac which is a pain, but at least it saves all those writes to your disk

Yes, can confirm, this is the first "solution" that works on Sierra.
MacOS 10.12.6 - DisplayLink 3.1

[benwen]

Originally Posted by duncanm

As a temporary fix you can enter the following in your terminal:

sudo log config --process=[PID] --mode "level:off"

where [PID] is the ID of the process you see in the console.

You have to re-do it every time you re-start your mac which is a pain, but at least it saves all those writes to your disk

Thank you duncamn!

Here's a quick and dirty shell script to automate the finding of the PID

#!/bin/sh
pid=`ps -ax | awk '/SkyLight.framework/ && !/awk/ {print $1}'`
echo "Skylight.framework with OpenGL logorrhea PID found. Suppressing log for PID $pid"
sudo log config --process=$pid --mode "level:off"

Put that in a file 'quite-dlink' in your $PATH, chmod 0755 it and execute it in Terminal at startup.

[paultzirides]

After installing the 4.0 beta, I'm no longer noticing any log spam. I ran the terminal command anyway, but observed no change in the amount or type of logs being generated by the system. Is anyone else seeing the same?

[dude123]

Problem solved!!!

Update to 4.0 didn't make it better on macOS 10.12 - BUT after the system update to 10.13 combined with 4.0 - now finally the log spam is solved and on top of that also the hardware support for video etc is very much improved.

Well done!! Thank you a lot DisplayLink-Team!!!!

[jormsby]

My new MacBook Pro running 10.12.6 and with DisplayLink 4.0.0 is filling up my Console with this error message.

I see where 10.13 might fix it but that is not an option on this work computer.

Any suggestions on how to get this to stop?

[mattbehnken]

Originally Posted by dude123

Problem solved!!!

Update to 4.0 didn't make it better on macOS 10.12 - BUT after the system update to 10.13 combined with 4.0 - now finally the log spam is solved and on top of that also the hardware support for video etc is very much improved.

Well done!! Thank you a lot DisplayLink-Team!!!!

My logs are filled with 3 per second. Since my log issue is slightly different than the OP I'll post it as an example. I'm not entirely sure it's DisplayLink, but I'm pretty sure.

MacOS High Sierra 10.13.2 - Display Link version 4.0 (sept. newest) with separate spaces checked (enabled)

I was able to suppress log until reboot using: sudo log config --pid=211 --mode "level:off"

Edit:

But you need to lookup the pid every boot, level:off

More Mac log suppression info

http://www.mackungfu.org/TurnoffrunawayloggingonmacOS

Speaking of log spam in High Sierra, I also get month 13 is out of bounds lol, but not as frequently as this:

default 19:04:19.044518 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.
default 19:04:19.044619 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.
default 19:04:19.044671 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.
default 19:04:19.044733 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.
default 19:04:19.044787 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.
default 19:04:19.060220 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.
default 19:04:19.060305 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.
default 19:04:19.060346 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.
default 19:04:19.060396 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.
default 19:04:19.060439 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.
default 19:04:19.153381 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.
default 19:04:19.153478 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.
default 19:04:19.153520 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.
default 19:04:19.153570 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.
default 19:04:19.153614 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.
default 19:04:19.163336 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.
default 19:04:19.163424 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.
default 19:04:19.169631 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.
default 19:04:19.169675 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.
default 19:04:19.169843 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.
default 19:04:19.224995 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.
default 19:04:19.225121 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.
default 19:04:19.225161 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.
default 19:04:19.225210 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.
default 19:04:19.225253 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.
default 19:04:19.421640 -0700 WindowServer No matching context for device (0x7f898cc3dcb0) - disabling acceleration.

[skew4]

Originally Posted by dude123

Problem solved!!!

Update to 4.0 didn't make it better on macOS 10.12 - BUT after the system update to 10.13 combined with 4.0 - now finally the log spam is solved and on top of that also the hardware support for video etc is very much improved.

Well done!! Thank you a lot DisplayLink-Team!!!!

Errr... I think you meant: Thank you Apple ! :-)

Some people have expressed concerned about wearing out disks. I don't know about that, however there's another massive difference that the super useful "log config level off" workaround just made: *responsiveness*. The short but still very painful lag between the moment I hit the keyboard and characters appears on the screen is finally gone.

For months and months until I found this message in the logs by chance (while looking for something else) I've been telling all my colleagues that DisplayLink was a technology really not for everyone because of a severe trade-off to make between screen real estate and responsiveness. Now I understand it was actually just that logging issue.

Has Apple any plan to backport the fix to Sierra?

Has DisplayLink updated their test plans to include responsiveness? (and also logging why not)