Since update to macOS 27 replicatord is running at 100% CPU on one of the efficiency cores of my Macbook M1 Pro. Tried killing the process and restarting my mac a few times without success. Does anyone else also experience this behavior? Any idea how to solve it?
I could of course disable the LaunchAgent/LaunchDaemon, but I don't know whether this would cause some other trouble.
Thanks in advance
MacBook Pro 14″, macOS 27.0
Thanks for the hint regarding process sampling. The sample showed that the CPU time is nearly completely spent in SQLLite database access, so I assume the database might be corrupted. Using lsof I found out that the database is located in
/Users/<my user>/Library/Group Containers/group.com.apple.replicatord/replicatord/
I renamed the three files belonging to the database
replicatord.sql-shm
replicatord.sql-wal
replicatord.sql
to something else (to have a copy available if needed and then killed replicatord. After a few seconds the process came back and created a fresh db. CPU consumption now is back to normal.
Thanks for the hint regarding process sampling. The sample showed that the CPU time is nearly completely spent in SQLLite database access, so I assume the database might be corrupted. Using lsof I found out that the database is located in
/Users/<my user>/Library/Group Containers/group.com.apple.replicatord/replicatord/
I renamed the three files belonging to the database
replicatord.sql-shm
replicatord.sql-wal
replicatord.sql
to something else (to have a copy available if needed and then killed replicatord. After a few seconds the process came back and created a fresh db. CPU consumption now is back to normal.
replicatord is an Apple system process, so I would leave its LaunchAgent/LaunchDaemon enabled while investigating rather than disable it as an initial workaround.
Apple notes that launchd manages system daemons and agents, including Apple-supplied system components. (Apple Support)
Since restarting replicatord and restarting the Mac have not resolved the sustained CPU usage, I would first test whether the behaviour also occurs in Safe Mode.
On an Apple-silicon Mac, shut down, press and hold the power button until the startup options appear, select the startup volume, hold Shift, and choose Continue in Safe Mode.
Apple explains that Safe Mode can help determine whether software loaded during startup is contributing to a problem. (Apple Support)
If replicatord is still using approximately 100% CPU in Safe Mode, that would be useful evidence that the behaviour is not simply caused by software loaded during a normal startup.
If the CPU usage disappears, the next investigation should focus on software or services loaded during a normal startup.
If the problem persists in normal mode, select replicatord in Activity Monitor while it is using high CPU and choose View >> Sample Process.
Apple documents Activity Monitor as a way to examine CPU activity and processes using processor resources. (Apple Support)
The Safe Mode result, Activity Monitor sample, should provide a much better basis for determining what is happening before changing or disabling the system service.
replicatord running at 100% CPU on macOS 27
