Update: I found an apparent correlation between the 100% DisplayLink CPU usage and the use of `.sharingType = .none` on a high-priority `NSWindow` in a macOS app while "Auto-detect video call overlays" is enabled.
BetterDisplay has an option to "Prevent overlays from affecting screenshots and screen recordings" - when this is enabled and BetterDisplay is configured to use overlay effects, the app uses `.sharingType = .none` on overlay NSWindow objects. This somehow seems to trigger the 100% CPU DisplayLink driver problem (- most of the times but strangely not always).
In upcoming app versions I'll set this setting to disabled by default - hopefully this will improve things. I post this info here as it might help the DisplayLink team to double down on this issue or figure out the root cause as probably other apps are affected too (configuring a high priority window with `.sharingType = .none` is normal and should not cause an issue like this).
|