I updated to 14.2 yesterday, and after a few hours I noticed that there were 2 processes that seem stuck: IMDPersistenceAgent and imagent
The former is using some 8-10% CPU while the latter constantly restarts after a short while, goes up to 3-4% and repeats. I've been searching around, and they seem related to message and address book syncing, as well as checking for incoming FaceTime calls. I've checked the Messages app, and the sync button is indeed greyed out and won't return...
When I check the console(Analytics Data), I see "com.apple.AddressBook.accounts.summary" being the source for spamming a lot of entries related to just message and address book syncing. A few of the entries also have the mentioned processes as source. But when I look closer, before 14.2 it sent "Address Book event completed. Changes: 0 (0/0/0)." every other hour, and now after 14.2 it hasn't once. Just seems to get stuck at something I can't see which is probably causing the processes to go haywire...
I've rebooted 3 times (including for the update) since yesterday, and it won't stop. Has anyone else seen this since the update and/or know how to solve it?
The former is using some 8-10% CPU while the latter constantly restarts after a short while, goes up to 3-4% and repeats. I've been searching around, and they seem related to message and address book syncing, as well as checking for incoming FaceTime calls. I've checked the Messages app, and the sync button is indeed greyed out and won't return...
When I check the console(Analytics Data), I see "com.apple.AddressBook.accounts.summary" being the source for spamming a lot of entries related to just message and address book syncing. A few of the entries also have the mentioned processes as source. But when I look closer, before 14.2 it sent "Address Book event completed. Changes: 0 (0/0/0)." every other hour, and now after 14.2 it hasn't once. Just seems to get stuck at something I can't see which is probably causing the processes to go haywire...
I've rebooted 3 times (including for the update) since yesterday, and it won't stop. Has anyone else seen this since the update and/or know how to solve it?
Last edited: