chronod keeps using 100% + CPU in macos Sequoia 15.4
by Poster
Apr 1, 2025
25
After updating macos Sequoia 15.4 today, I found that the chronod process has been consuming a lot of CPU, which is very troubling.
Process at:/System/Library/PrivateFrameworks/ChronoCore.framework/Support/chronod
https://i.imgur.com/NdCfxR3.png
All the solutions on ChatGPT have been tried, including:
1. Restart macOS
2. Turn off the "Screen Time" function
3. Delete Screen Time logs and configuration files
4. Reset chronod cache and configuration
5. This situation also occurs when entering safe mode
6. Reinstall the system (but every time it suddenly restarts and tells me that the reinstallation was not successful.)
I really don't understand where the sudden problem appears. It has always been fine before. Has any MacOS boss ever had this situation and knows how to solve it?
Replies
-
Poster Apr 1, 2025The following is ChatGPT's analysis report after reading the logs: From this report, we can see that ` chronod ` is performing operations related to multiple threads and services, especially activities related to ` ReplicatorServices `. Analyze the key information: ### 1. * * Replicator Services * * -The service is performing a large number of object and data transfer operations. According to the stack trace, it involves some Swift frameworks (such as Combine) and often performs system calls such as ` dispatch _ sync ` and ` mach _ msg `, which are usually operations related to thread and task scheduling. -Frequent memory allocation and release operations may be associated with copying and synchronizing large amounts of data, leading to system performance problems. These operations can consume a lot of CPU resources. ### 2. * * Core Foundation and BaseBoard * * -Multiple function calls in ` BaseBoard ` and ` CoreFoundation ` such as ` NSKeyedArchiver ` and ` CFPrefsPlistSource ` are also mentioned in the report. These functions involve setting management and data storage, which may be one of the factors leading to performance problems. ### 3. * * Threading and scheduling * * Multiple threads are involved in multiple places in the report (e.g. ` DispatchQueue ` and ` pthread _ wqthread `). These threads may lead to excessive context switching and increased CPU usage while waiting and scheduling tasks. --- # # # Recommended further solutions: 1. * * Optimize ReplicatorServices operations * * Try to reduce the load on ` ReplicatorServices ` by reducing the frequency of data replication, or optimizing the data synchronization logic. 2. * * Check if there are redundant threads or tasks * * By checking if there are too many background tasks or threads, you can reduce unnecessary computational load. 3. * * Monitor CoreFoundation and BaseBoard usage * * If these modules involve frequent data reads and writes or profile operations, the burden can be reduced by adjusting settings or reducing the frequency of profile updates. > These actions may require further confirmation through debugging tools to find more specific bottlenecks.
-
Anonymous3741 Apr 1, 2025The cpu of the second notification center is also a bit high, which is related to widgets like chronod. Is there some sort of unusual widgets enabled (ios widgets for example?) that causes "a lot of object and data transfer operations" when data is synchronized? After looking at the% cpu of these two, both are 0
-
Poster Apr 1, 2025@ Anonymous3741 I have deleted all the widgets, and it will be the same. However, I guess it's because I used the Widget function of Airbuddy Beta, but I have uninstalled it and the situation remains the same.
-
Anonymous1772 Apr 2, 2025I canceled the update when I downloaded to 80% yesterday. It seems that this sixth sense is right
-
Anonymous6514 Apr 2, 2025Me too, updated yesterday...
-
Anonymous6514 Apr 2, 2025[Chronod on Mac: Part of macOS or Malware?] (https://iboysoft.com/wiki/chronod.html)
-
Poster Apr 2, 2025Is @ Anonymous6514 solved now? Mine is still like this. If I do this again, I guess I will have to empty and rebrush the system.
-
Anonymous6514 Apr 2, 2025@ Poster # 7 No, I brushed it from RC to the official version, it still doesn't work, restart is still the same...
-
Anonymous3741 Apr 2, 2025@ Poster looked at it again. After the update and restart (the two were one day ago and 2 hours ago respectively), although the% CPU of the current chronod is 0, the CPU time is as high as the third place (after google chrome and identityserviced), indicating that it has been higher. So do you need to wait patiently for a while, and maybe it will return to normal after completing a specific task?
-
Poster Apr 2, 2025@ Anonymous3741 has tossed this problem too much. I don't know what kind of moth Apple has come up with. At present, I haven't seen anyone else having the same problem.
-
Poster Apr 2, 2025@ Anonymous6514 Does Chronod suddenly pop up and occupy more than 100% as soon as you restart it, and then appear over and over again? Can you take a screenshot for my reference?
-
Poster Apr 2, 2025@ Anonymous6515 I don't know if it's for this reason, but the Airbuddy I installed is useful to Now Playing's Widget
-
Anonymous6516 Apr 3, 2025I suspect it is caused by the widget of bettertouchtool, but it will be fine after restarting btt
-
Poster Apr 3, 2025@ Anonymous6516 I don't have this App, I think it must be a problem with this system version
-
Anonymous6514 Apr 3, 2025@ Poster # 12 It shouldn't be. I didn't install new programs before and after the upgrade, including adding new widgets. This is intermittent. I restarted it five times yesterday. It was better for a while in the middle, but it appeared again today
-
Anonymous6514 Apr 3, 2025Brothers, 15.5 Beta is out, do you want to try it?
-
Poster Apr 3, 2025@ Anonymous6514 Why don't you try it first? I'll upgrade immediately if it's okay.
-
Anonymous6514 Apr 3, 2025@ Poster # 17 I have upgraded and currently works fine
-
Anonymous6514 Apr 3, 2025@ Anonymous6514 # 18 Then he was slapped in the face for half an hour, and chronod was pulled up again
-
Poster Apr 3, 2025@ Anonymous6514 Can you take a screenshot and see how much is it? I'm afraid our computer has been broken by this process