mirror of
https://github.com/MonitorControl/MonitorControl.git
synced 2026-05-15 14:15:55 -06:00
[GH-ISSUE #1065] MonitorControl crashes with a trace trap message when mac comes out of monitor sleep #635
Labels
No labels
Status: Abandoned
arm64
beta
beta
bug
done
duplicate
enhancement
feedback needed from reporter
in progress
invalid
investigating
known Issue
monitor Issue
pull-request
translation
unable to reproduce
unreleased
x86
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/MonitorControl#635
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @waydabber on GitHub (Jun 3, 2022).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1065
Discussed in https://github.com/MonitorControl/MonitorControl/discussions/1063
Originally posted by ivahos June 3, 2022
Hi
I have discovered a bug when running monitorcontrol on my mac studio. Sometimes the mac uses a longer time than normal to detect the monitor after a monitor sleep, when this happens MonitorControl often crashes.
ivar@Jumbo MacOS % ./MonitorControl
zsh: trace trap ./MonitorControl
I have created a workaround by starting the app from a shell script that keeps relaunching it whenever it quits.
MonitorControl-2022-06-03-111213.ips.zip
I am attaching the crash log from the console app.
@balintant commented on GitHub (Oct 22, 2022):
Experiencing this even at a clean start. Downgrade to 4.0.x works.
(M1 Pro, Ventura RC, LED Cinema Display 27")
@adipierro commented on GitHub (Feb 17, 2023):
Crash occurs when the display is connected with internal HDMI port.
@stale[bot] commented on GitHub (Feb 18, 2024):
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require attention? This issue may be closed if no further activity occurs. Thank you for your contributions.