com.apple.cmio.AppleCameraAssistant constantly respawning
The launchd.log is spammed by output of the AppleCameraAssistant every second.
Example:
...
2023-05-22 21:48:59.801689 (system/com.apple.cmio.AppleCameraAssistant) <Notice>: service state: spawning
2023-05-22 21:48:59.801734 (system/com.apple.cmio.AppleCameraAssistant) <Notice>: launching: ipc (mach)
2023-05-22 21:48:59.803165 (system/com.apple.cmio.AppleCameraAssistant [11277]) <Notice>: xpcproxy spawned with pid 11277
2023-05-22 21:48:59.803202 (system/com.apple.cmio.AppleCameraAssistant [11277]) <Notice>: internal event: SPAWNED, code = 0
2023-05-22 21:48:59.803210 (system/com.apple.cmio.AppleCameraAssistant [11277]) <Notice>: service state: xpcproxy
2023-05-22 21:48:59.803220 (system/com.apple.cmio.AppleCameraAssistant [11277]) <Notice>: deferred event: domain spawn response: 0
2023-05-22 21:48:59.803229 (system/com.apple.cmio.AppleCameraAssistant [11277]) <Notice>: internal event: SOURCE_ATTACH, code = 0
2023-05-22 21:48:59.816284 (system/com.apple.cmio.AppleCameraAssistant [11277]) <Notice>: service state: running
2023-05-22 21:48:59.816302 (system/com.apple.cmio.AppleCameraAssistant [11277]) <Notice>: internal event: INIT, code = 0
2023-05-22 21:48:59.816314 (system/com.apple.cmio.AppleCameraAssistant [11277]) <Notice>: Successfully spawned AppleCameraAssistant[11277] because ipc (mach)
2023-05-22 21:48:59.865134 (pid/11277 [AppleCameraAssi]) <Notice>: uncorking exec source upfront
2023-05-22 21:48:59.865159 (pid/11277 [AppleCameraAssi]) <Notice>: created
2023-05-22 21:48:59.877588 (system/com.apple.cmio.AppleCameraAssistant [11277]) <Notice>: exited due to exit(0)
2023-05-22 21:48:59.877611 (system/com.apple.cmio.AppleCameraAssistant [11277]) <Notice>: service state: exited
2023-05-22 21:48:59.877620 (system/com.apple.cmio.AppleCameraAssistant [11277]) <Notice>: internal event: EXITED, code = 0
2023-05-22 21:48:59.877625 (system) <Notice>: service inactive: com.apple.cmio.AppleCameraAssistant
2023-05-22 21:48:59.877644 (system/com.apple.cmio.AppleCameraAssistant [11277]) <Notice>: service state: not running
2023-05-22 21:48:59.877654 (pid/11277 [AppleCameraAssi]) <Notice>: shutting down
2023-05-22 21:48:59.877663 (pid/11277 [AppleCameraAssi]) <Notice>: cleaning up
2023-05-22 21:48:59.877673 (system/com.apple.cmio.AppleCameraAssistant) <Notice>: Service only ran for 0 seconds. Pushing respawn out by 1 seconds.
2023-05-22 21:48:59.877740 (system/com.apple.cmio.AppleCameraAssistant) <Notice>: internal event: WILL_SPAWN, code = 0
2023-05-22 21:48:59.877777 (system/com.apple.cmio.AppleCameraAssistant) <Notice>: service state: spawn scheduled
2023-05-22 21:48:59.877779 (system/com.apple.cmio.AppleCameraAssistant) <Notice>: service throttled by 1 seconds
2023-05-22 21:48:59.877787 (system) <Notice>: removing child: pid/11277
...
I found several references to people having the same issue on the internet, e.g
- https://www.mactechnews.de/forum/discussion/AppleCameraAssistant-spuckt-die-Log-Files-voll-348330.html
- https://forums.macrumors.com/threads/applecameraassistant-flooding-the-log-files.2378639/
- https://www.reddit.com/r/MacOSBeta/comments/109fvqg/132b2_applecameraassistant_looping_constantly/
Unfortunately, those were not helpful. In fact, I am using an Electron app (Signal Desktop Client) as the WhatsApp client was mentioned as a possible culprit, but even uninstalling Signal and rebooting the Mac did not fix the issue. I also created another "clean" dummy user but could still see the problem.
As I understand the constant logging will not necessarily produce a significant wear on the SSD as the launchd log files are supposedly kept in a ramdisk. However, I would still like to be able to either prevent the service from being started at all, or at least reduce the log verbosity. Apparently, this will require me to disable SIP completely which is not a great thing.
The integrated camera is working flawlessly, by the way.
Does anyone have any suggestions on how to tackle this issue?
Thanks in advance
Jörg
MacBook Air 13″