[GH-ISSUE #174] Choppiness; high CPU usage when connecting monitor. #127

Closed
opened 2026-05-05 05:13:02 -06:00 by gitea-mirror · 1 comment
Owner

Originally created by @HunterJKirby on GitHub (Jan 26, 2020).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/174

When a new monitor is connected, activity monitor shows MonitorControl as "not responding" and using 50-75% of CPU. During this time the dropped frames cause the monitors to be worthless for 10-15 seconds before MonitorControl starts responding again and CPU usage drops to 0.1%.

Originally created by @HunterJKirby on GitHub (Jan 26, 2020). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/174 When a new monitor is connected, activity monitor shows MonitorControl as "not responding" and using 50-75% of CPU. During this time the dropped frames cause the monitors to be worthless for 10-15 seconds before MonitorControl starts responding again and CPU usage drops to 0.1%.
Author
Owner

@HunterJKirby commented on GitHub (Jan 26, 2020):

Fixed by disabling polling

<!-- gh-comment-id:578477277 --> @HunterJKirby commented on GitHub (Jan 26, 2020): Fixed by disabling polling
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/MonitorControl#127
No description provided.