CalendarAgent & CalNCService eating CPU time

Discussion in 'macOS Sierra (10.12)' started by larrymac1108, Aug 3, 2016.

  1. larrymac1108 macrumors newbie

    Aug 3, 2016
    Is any one else having the problem when running on WiFi that the CalendarAgent and CALNCService processes are consuming over 70% of the CPU? The problem goes away when connected to a LAN via the Thunderbolt port.

    Just started when updated to Beta 3 last night.
  2. HauerDMD macrumors newbie

    May 31, 2016
    I am experiencing the exact same issue with CalendarAgent. Computer runs hot and fans blasting. No bueno.
  3. larrymac1108 thread starter macrumors newbie

    Aug 3, 2016
    I fixed this issue on mine this morning. Discovered where the issue was by trying to use the Calendar app and it was constantly going in to "Not Responding" mode. Disconnected from the network completely and then started Calendar app and went to preferences, which brings up "Internet Account" in System Preferences. While going through the account when I went to Game Center it received an error "NURL... -1009". As I do not use Game Center, I delete the account, closed the Calendar and plugged back into the network and the problem has not come back over the last hour.
  4. bbbggg macrumors newbie


    Aug 18, 2016
    I'm on Beta 6 on a 2009 MBP. CalNCService and CalendarAgent both spike my CPU like crazy. I tried deleting the Game Center in Internet Accounts. Didn't do anything. I have iCloud Calendar turned off, and Google Calendar turned on. Any ideas?
  5. gluigi53 macrumors newbie

    Jan 2, 2018
    [QUOTE = "bbbggg, post: 23257069, membro: 1040840"] Sono su Beta 6 su un MBP 2009. CalNCService e CalendarAgent stimolano la mia CPU come un matto. Ho provato a eliminare il Game Center negli account Internet. Non ho fatto niente Ho disattivato il calendario di iCloud e Google Calendar è attivo. Qualche idea? [/ QUOTE]

    Ho seguito la procedura, ma il problema rimane. Possibile che Apple non faccia nulla!!!????
  6. berto macrumors newbie

    Mar 28, 2008
    This was a big pain to sort out. My problem: shared calendars.

    I ended up having to "leave" all shared calendars and have the owner re-share with me. :(

    Problem is fixed now.

Share This Page