calaccessd consuming excessive CPU & memory with Outlook accounts in Sequoia

Question

Level 1

8 points

calaccessd consuming excessive CPU & memory with Outlook accounts in Sequoia

As soon as I booted up after updating to Sequoia (15.0), began noticing "calaccessd" process constantly consuming 12.5% of CPU (equal to 100% of one Performance Core, 25% of all 4 performance cores, or so on between my M1 8 cores), as well as a significant increase (~30%) in compressed memory.

I've been able to pin the culprit specifically to my "Exchange" (M365 personal Outlook) account, even if I disable Calendar syncing. Apparently not affected by Google or Yahoo accounts.

Only workaround I've found is to completely avoid adding the M365 account to MacOS.

Hope this bug is fixed soon.

MacBook Air (M1, 2020)

Posted on Sep 21, 2024 8:26 PM

Reply

Answer 1

Oct 24, 2024 10:12 AM in response to bernxAU

it started biting me a couple of weeks after two developer updates ago. But I seem to have it worse.

If left running, I eventually get an "out of memory" error, with Mail taking something like 50g of RAM.

Before that happens, it tends to quickly go over 100% cpu, until it seems to top out at 400%, occasionally dipping down to 350%. If I leave mail on while it's asleep overnight, I have a hot battery in the morning (unless it's not plugged in, in which case I have an empty battery).

I don't have any Microsoft accounts; they are either gmail, gmail hosted, dreamhost, or iCloud.

I've tried taking all accounts offline, which seems to help, but isn't particularly useful.

I rebuilt one account with no issue, but then I tried to rebuild the iCloud account, and it quickly shot to 60% or so.

Also, regular quit, either from within the application or monitor, fails every time; forced or kill -9 is necessary.

This is on an 8G M3 13" MacBook

Reply

Answer 2

bernxAU Author

Level 1

8 points

Sep 21, 2024 8:45 PM in response to bernxAU

What's worse, even without Outlook altogether, each time I try to use Calendar, calaccessd remains running, pegged at 12.5% [total] CPU and increasing its Memory usage until manually shutdown or (I guess) by the OS.

Reply