Hazel throws beachball when opening rule criteria

Is anyone else have the more than occasional issue where double-clicking a rule within the Hazel pref pane results in ~5-minute spinning beach ball? Eventually the rule opens and the criteria become visible as though there were no problem--but clearly something must be happening because the beachball isn't just spinning for no reason.
On a related note, I have noticed the same behavior when I try to use the 'Add Tag' action. The moment I start to type into the text box to find an existing tag name or define a new one, I get the beachball for a solid 5ish minutes.
In case this is related, I just found this in Console for HazelHelper (user), however the timestamp doesn't coincide with the most recent incidence of this behavior:
I also have a HazelHelper (com.apple.os_debug_log) item in my Console list and the single item in there is the following:
Anyone have insight?
On a related note, I have noticed the same behavior when I try to use the 'Add Tag' action. The moment I start to type into the text box to find an existing tag name or define a new one, I get the beachball for a solid 5ish minutes.
In case this is related, I just found this in Console for HazelHelper (user), however the timestamp doesn't coincide with the most recent incidence of this behavior:
- Code: Select all
objc[458]: Class FIFinderSyncExtensionHost is implemented in both /System/Library/PrivateFrameworks/FinderKit.framework/Versions/A/FinderKit (0x7fff9fbcd3d8) and /System/Library/PrivateFrameworks/FileProvider.framework/OverrideBundles/FinderSyncCollaborationFileProviderOverride.bundle/Contents/MacOS/FinderSyncCollaborationFileProviderOverride (0x110cd8f50). One of the two will be used. Which one is undefined.
I also have a HazelHelper (com.apple.os_debug_log) item in my Console list and the single item in there is the following:
- Code: Select all
assertion failed: 18G2022: libxpc.dylib + 90677 [7DEE2300-6D8E-3C00-9C63-E3E80D56B0C4]: 0x89
Anyone have insight?