I'd noticed Calendr quitting many times a minute for a hour or so. Seems it fixed itself by CalendarLauncher crashing! 🤣 Cunning.
Process: CalendrLauncher [48078]
Path: /Users/USER/*/Calendr.app/Contents/MacOS/CalendrLauncher.app/Contents/MacOS/CalendrLauncher
Identifier: br.paker.Calendr.launcher
Version: 1.0 (1)
Code Type: ARM-64 (Native)
Role: Default
Parent Process: launchd [1]
Coalition: br.paker.Calendr.launcher [1201]
User ID: 501
Date/Time: 2026-07-27 14:20:47.2197 +0100
Launch Time: 2026-07-27 14:20:47.1445 +0100
Hardware Model: Mac14,3
OS Version: macOS 26.3 (25D125)
Release Type: User
Crash Reporter Key: FB8D227F-16E8-9D99-XXXX-9FBCE749603C
Incident Identifier: 9E976C60-79BB-4E33-XXXX-1DF90A8AB3B6
Sleep/Wake UUID: 61401041-0B8E-4C41-XXXX-A94D4580BFE8
Time Awake Since Boot: 2200000 seconds
Time Since Wake: 4568 seconds
System Integrity Protection: enabled
Triggered by Thread: 0, Dispatch Queue: com.apple.main-thread
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000001, 0x00000001a151b9d4
Termination Reason: Namespace SIGNAL, Code 5, Trace/BPT trap: 5
Terminating Process: exc handler [48078]
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libswiftCore.dylib 0x1a151b9d4 _assertionFailure(_:_:file:line:flags:) + 176
1 libswiftCore.dylib 0x1a15c7f8c swift_errorInMain + 604
2 libswift_Concurrency.dylib 0x28d32a4f0 swift::runJobInEstablishedExecutorContext(swift::Job*) + 288
3 libswift_Concurrency.dylib 0x28d32b8e4 swift_job_runImpl(swift::Job*, swift::SerialExecutorRef) + 156
4 libdispatch.dylib 0x18de5dff4 _dispatch_main_queue_drain.cold.5 + 592
5 libdispatch.dylib 0x18de35f48 _dispatch_main_queue_drain + 180
6 libdispatch.dylib 0x18de35e84 _dispatch_main_queue_callback_4CF + 44
7 CoreFoundation 0x18e0ac9a0 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 16
8 CoreFoundation 0x18e0817fc __CFRunLoopRun + 1944
9 CoreFoundation 0x18e13bf3c _CFRunLoopRunSpecificWithOptions + 532
10 CoreFoundation 0x18e0d4a50 CFRunLoopRun + 64
11 libswift_Concurrency.dylib 0x28d313b04 CFMainExecutor.run() + 48
12 libswift_Concurrency.dylib 0x28d3137bc protocol witness for RunLoopExecutor.run() in conformance DispatchMainExecutor + 48
13 libswift_Concurrency.dylib 0x28d313bb0 swift_task_asyncMainDrainQueueImpl + 108
14 libswift_Concurrency.dylib 0x28d333690 swift_task_asyncMainDrainQueue + 92
15 CalendrLauncher 0x104a7100c 0x104a70000 + 4108
16 dyld 0x18dc19d54 start + 7184
(Relaunching, I see Console mentions No windows open yet 14:27:12.324183+0100 Calendr void _NSDisableAutomaticTerminationAndLog(NSString *) No windows open yet, does that encourage the OS to think killing Calendr is ok?) Actually, NO. Other menu extras say this and don't get killed.
Now Calendr doesn't relaunch when it is killed. :-(
Here's excerpts from Console for one of its deaths:
default 14:35:01.561464+0100 deleted Received state update for 48264 (app<application.br.paker.Calendr.141512308.141512323(501)>, running-active-NotVisible
default 14:35:01.561829+0100 runningboardd Received termination request from [osservice<com.apple.cache_delete(501)>:4120] on <RBSProcessPredicate <RBSProcessBundleIdentifierPredicate "br.paker.Calendr">> with context <RBSTerminateContext| code:0xBADDD15C explanation:CacheDeleteAppContainerCaches requesting termination assertion for br.paker.Calendr reportType:None maxTerminationResistance:NonInteractive attrs:[
<RBSPreventLaunchLimitation| <RBSProcessPredicate <RBSProcessBundleIdentifierPredicate "br.paker.Calendr">> allow:(null)>
]>
default 14:35:01.569915+0100 runningboardd Acquiring assertion targeting system from originator [osservice<com.apple.cache_delete(501)>:4120] with description <RBSAssertionDescriptor| "CacheDeleteAppContainerCaches requesting termination assertion for br.paker.Calendr" ID:411-4120-3984650 target:system attributes:[
<RBSPreventLaunchLimitation| <RBSProcessPredicate <RBSProcessBundleIdentifierPredicate "br.paker.Calendr">> allow:(null)>
]>
default 14:35:01.579494+0100 runningboardd Executing termination request for: <RBSProcessPredicate <RBSProcessBundleIdentifierPredicate "br.paker.Calendr">>
default 14:35:01.600238+0100 runningboardd [app<application.br.paker.Calendr.141512308.141512323(501)>:48264] Terminating with context: <RBSTerminateContext| code:0xBADDD15C explanation:CacheDeleteAppContainerCaches requesting termination assertion for br.paker.Calendr reportType:None maxTerminationResistance:NonInteractive attrs:[
<RBSPreventLaunchLimitation| <RBSProcessPredicate <RBSProcessBundleIdentifierPredicate "br.paker.Calendr">> allow:(null)>
]>
default 14:35:01.601464+0100 WindowServer 0[outside of RPC]: Process death: 0x0-0x2259257 (Calendr) connectionID: 3FB0DB pid: 48264 in session 0x101
default 14:35:01.601500+0100 WindowServer <BSCompoundAssertion:0x7a3405500> ([FocusManager:257]-deferringPolicyEvaluationSuppression) acquire for reason:process death - 0x0-0x2259257 (Calendr) acq:0x7a2ae15a0 count:1
default 14:35:01.604245+0100 WindowServer 0[outside of RPC]: [FocusManager:257] update to deferring policy requested for reason: permitted list updated - 0x0-0x2259257 removed - but we are suppressing evaluation for reasons: {(
"process death - 0x0-0x2259257 (Calendr)"
)}
default 14:35:01.602943+0100 WindowManager Connection invalidated | (48264) Calendr
default 14:35:01.603768+0100 ControlCenter [app<application.br.paker.Calendr.141512308.141512323>:48264] Workspace connection invalidated.
default 14:35:01.603786+0100 ControlCenter [app<application.br.paker.Calendr.141512308.141512323>:48264] Now flagged as pending exit for reason: workspace client connection invalidated
default 14:35:01.606345+0100 WindowServer 0[outside of RPC]: [FocusManager:257] update to deferring policy requested for reason: permitted list updated - 0x1-0xbc88 removed - but we are suppressing evaluation for reasons: {(
"process death - 0x0-0x2259257 (Calendr)"
)}
default 14:35:01.608647+0100 kernel SK[2]: ch_close_common ch 0x0 (flowswitch:com.apple.nexus.flowswitch:"fsw_en1[9]_Calendr.48264":9:-1) uuid 0B3B11BC-6CA3-42C8-BFAF-4D4580D98E2E flags 0x11
default 14:35:01.611785+0100 runningboardd [app<application.br.paker.Calendr.141512308.141512323(501)>:48264] terminate_with_reason() success
default 14:35:01.613374+0100 runningboardd [app<application.br.paker.Calendr.141512308.141512323(501)>:48264] termination reported by launchd (15, 3135099228, 9)
default 14:35:01.613806+0100 runningboardd Removing process: [app<application.br.paker.Calendr.141512308.141512323(501)>:48264]
default 14:35:01.614027+0100 runningboardd Removing launch job for: [app<application.br.paker.Calendr.141512308.141512323(501)>:48264]
default 14:35:01.614223+0100 runningboardd Removed job for [app<application.br.paker.Calendr.141512308.141512323(501)>:48264]
default 14:35:01.614263+0100 runningboardd Removing assertions for terminated process: [app<application.br.paker.Calendr.141512308.141512323(501)>:48264]
default 14:35:01.616913+0100 runningboardd XPC connection invalidated: [app<application.br.paker.Calendr.141512308.141512323(501)>:48264]
default 14:35:01.622978+0100 runningboardd No connection found to send inheritance for process [app<application.br.paker.Calendr.141512308.141512323(501)>:48264] with changeSet: <RBSInheritanceChangeSet| gained:(null) lost:{(
<RBSInheritance| environment:(none) name:com.apple.boardservices.endpoint-injection origID:411-641-3984615 payload 8302653173122775812>,
<RBSInheritance| environment:(none) name:com.apple.launchservices.userfacing origID:411-377-3984613 0>
)}>
default 14:35:01.634383+0100 runningboardd Calculated state for app<application.br.paker.Calendr.141512308.141512323(501)>: none (role: None) (endowments: (null))
default 14:35:01.634679+0100 ControlCenter [app<application.br.paker.Calendr.141512308.141512323>:48264] Process exited: <RBSProcessExitContext| specific, status:<RBSProcessExitStatus| domain:runningboard(15) code:0xbaddd15c>>.
default 14:35:01.634696+0100 ControlCenter [app<application.br.paker.Calendr.141512308.141512323>:48264] Setting process task state to: Not Running
default 14:35:01.634710+0100 ControlCenter [app<application.br.paker.Calendr.141512308.141512323>:48264] Setting process visibility to: Unknown
default 14:35:01.634756+0100 ControlCenter [app<application.br.paker.Calendr.141512308.141512323>:48264] Invalidating workspace.
default 14:35:01.634809+0100 ControlCenter Removing source registration for processHandle: [app<application.br.paker.Calendr.141512308.141512323(501)>:48264]
default 14:35:01.634942+0100 ControlCenter Received state update for 48264 (app<application.br.paker.Calendr.141512308.141512323(501)>, none-NotVisible
default 14:35:01.635292+0100 ControlCenter Received state update for 48264 (app<application.br.paker.Calendr.141512308.141512323(501)>, none-NotVisible
default 14:35:01.635411+0100 ControlCenter Removing: <FBApplicationProcess: 0x9a5c24180; app<application.br.paker.Calendr.141512308.141512323>:48264(v115A70)>
default 14:35:01.634641+0100 runningboardd Calculated state for app<application.br.paker.Calendr.141512308.141512323(501)>: none (role: None) (endowments: (null))
I'd noticed Calendr quitting many times a minute for a hour or so. Seems it fixed itself by CalendarLauncher crashing! 🤣 Cunning.
(Relaunching, I see Console mentions No windows open yet
14:27:12.324183+0100 Calendr void _NSDisableAutomaticTerminationAndLog(NSString *) No windows open yet, does that encourage the OS to think killing Calendr is ok?) Actually, NO. Other menu extras say this and don't get killed.Now Calendr doesn't relaunch when it is killed. :-(
Here's excerpts from Console for one of its deaths: