log spam
Quote:
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. |
responsiveness
Quote:
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) |
Quote:
Code:
# log show --last 6h --predicate 'messageType == error and processImagePath endswith "DisplayLinkManager"' The fact that my monitors run at 60Hz is likely not a coincidence. |
All times are GMT. The time now is 03:30 PM. |
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2024, vBulletin Solutions, Inc.