I am using macOS 10.14.6. After certain actions, such as starting the screensaver and other "innocent" things, the system locks up for about a minute. The mouse pointer can be moved, but nothing else reacts or moves on screen. I just have to wait it out.
Looking at the console, I can see six
.crash files for
tccd, with timestamps about 10 seconds apart, after each such event. The contents are like this:
Process: tccd  Path: /System/Library/PrivateFrameworks/TCC.framework/Versions/A/Resources/tccd Identifier: tccd Version: 221.260.3 ... Crashed Thread: 1 Dispatch queue: com.apple.root.default-qos.overcommit Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY Application Specific Information: dyld3 mode *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[NSFileManager fileSystemRepresentationWithPath:]: nil or empty path argument' terminating with uncaught exception of type NSException abort() called
To trigger the problem, it is sufficient to open the Desktop & Screensaver preferences, which shows a preview of the screensaver.
UPDATE: Trying to choose the picture source for screensavers causes a several minutes long hang. It seems that the problem is with the screensaver trying to access data on disk. The picture source has always been set to the default though.
I have now completely disabled the screensaver to try to avoid this problem. But unfortunately, it is sometimes (non-reproducibly) triggered by other actions as well, typically either using dictionary lookup (with "force-click") or using quicklook in a file-chooser dialog. Of course, it always happens when I'm in a hurry and trying to get work done ...
What can I do to find the root cause of the problem, and resolve it?
This problem has persisted for several months now and I had no luck in diagnosing it, other than discovering the relationship to
tccd, which is responsible for controlling the access of programs to "sensitive" user data.
UPDATE: The same problem is reported here and claimed to be related to security update 2020-004.
What I tried so far:
- Reset the TCC database using
tccutil reset All.
- Here is it claimed that uninstalling Dropbox helped. I tried this and it made no difference.