DisplayLink Forum
Page 6 of 6 « First 45 6
Show 40 post(s) from this thread on one page

DisplayLink Forum (https://displaylink.org/forum/index.php)
-   Mac Software (https://displaylink.org/forum/forumdisplay.php?f=30)
-   -   Endless log spam _CGXGLDisplayContextForDisplayDevice: No matching context for device (https://displaylink.org/forum/showthread.php?t=62987)

mattbehnken 12-23-2017 05:54 PM
log spam
 
Quote:
Originally Posted by dude123 (Post 84273)
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 02-07-2018 01:11 AM
responsiveness
 
Quote:
Originally Posted by dude123 (Post 84273)
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)

skew4 02-08-2018 08:31 PM
Quote:
Originally Posted by dude123 (Post 83449)
My syslogs get hit by 60.000 messages per second.
Indeed:

Code:
# log show --last 6h --predicate 'messageType == error and processImagePath endswith "DisplayLinkManager"'

Timestamp                      Thread    Type        Activity            PID   
2018-02-08 09:34:12.277266  0xf609a    Error      0x0                  115    DisplayLinkManager: (CoreFoundation) Detected potentially harmful notification post rate of 60.0026 notifications per second
This message shows up even with the "level: off" workaround (but infrequently).

The fact that my monitors run at 60Hz is likely not a coincidence.


All times are GMT. The time now is 05:36 PM.
Page 6 of 6 « First 45 6
Show 40 post(s) from this thread on one page

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2024, vBulletin Solutions, Inc.