"Auto-detect video call overlays" - 100% CPU, lags, freezing issue

Szymon · 12-15-2025, 11:27 AM

Hi waydabber,

Microsoft Teams on macOS uses the NSWindow object with the property .sharingType = .none for screen sharing control. As a result, these windows are not visible on external DisplayLink screens. This become a hot issue in the beginning of this year. To address this DisplayLink implemented a workaround that detects such objects and makes them visible. However, this approach comes with a trade-off: reduced performance.

Ideally, Microsoft would resolve this issue in Teams for macOS, but so far, no fix has been provided. Apple explicitly recommends using SCContentFilter to exclude UI elements that are not intended for streaming, which seems like the proper solution.

Regards,
Szymon

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Switch to Linear Mode Switch to Hybrid Mode Threaded Mode

12-15-2025, 11:27 AM	#3
Szymon DisplayLink Tech Support Join Date: Feb 2010 Posts: 194	Hi waydabber, Microsoft Teams on macOS uses the NSWindow object with the property .sharingType = .none for screen sharing control. As a result, these windows are not visible on external DisplayLink screens. This become a hot issue in the beginning of this year. To address this DisplayLink implemented a workaround that detects such objects and makes them visible. However, this approach comes with a trade-off: reduced performance. Ideally, Microsoft would resolve this issue in Teams for macOS, but so far, no fix has been provided. Apple explicitly recommends using SCContentFilter to exclude UI elements that are not intended for streaming, which seems like the proper solution. Regards, Szymon