Le processus com.apple.Safari.History sature totalement la mémoire et le processeur avec Safari 17.1 sous macOS Ventura 13.6.1 (22G313)

Depuis les 2 dernières mises à jour de sécurité d'octobre 2023 pour macOS Ventura & Safari, le processus com.apple.Safari.History sature totalement la mémoire à 100% ainsi que le processeur avec un fichier qui fait le yoyo, entre 10Go et plus de 100Go ! Ce problème provient du processus de synchronisation iCloud pour Safari, si celui-ci est désactivé : le problème disparait. Il est donc clairement identifié. Seulement voilà, l'aide Apple ne propose qu'une seule solution – et toujours la même, quelques soit le problème – réinstaller macOS ou mettre à jour vers la version actuelle, soit macOS Sonoma (sans aucunne assurance que ça résolve le problème). Ce problème n'est pas nouveau, il remonte à plusieurs années, mais les solutions anciennes, ne fonctionnent plus, soit : Purger l'historique et les caches de Safari, forcer à quitter le processus com.apple.Safari.History via le moniteur d'activité. Lors d'un démarrage sur une session neutre ou en mode sans échec : le problème est identique. La réinstallation de macOS Ventura n'a pas résolu le problème.

Sur MacStudio M1 (32 RAM).


Est-ce que quelqu'un a une vraie solution qui fonctionne ?

Il n'est pas question de passer un Mac pour une utilisation professionnelle sur Sonoma à ce jour (2 nov. 2023).



Mac Studio (2023)

Posted on Nov 2, 2023 5:12 AM

Reply

Similar questions

10 replies

Nov 2, 2023 10:47 AM in response to GSF-MF

You've installed what most of the experienced contributors here consider to be akin to malware: CleanMyMac


First, there is no reason to ever install or run any 3rd party "cleaning", "optimizing", "speed-up", anti-virus, VPN or security apps on your Mac.  This documents describe what you need to know and do in order to protect your Mac: Effective defenses against malware and other threats - Apple Community and Recognize and avoid phishing messages, phony support calls, and other scams - Apple Support.  


There are no known viruses, i.e. self propagating, for Macs.  There are, however, adware and malware which require the user to install although unwittingly most of the time thru sneaky links, etc.   


Anti Virus developers try to group all types as viruses into their ad campaigns of fear.  They do a poor job of the detecting and isolating the adware and malware.  Since there are no viruses these apps use up a lot of system resources searching for what is non-existent and adversely affect system and app performance.


There is one app, Malwarebytes, which was developed by a long time contributor to these forums and a highly respected member of the computer security community, that is designed solely to seek out adware and known malware and remove it.  The free version is more than adequate for most users.  


Uninstall CleanMyMac according to the developer's instructions. You can check to see if you've removed all of the supporting files by downloading and running the shareware app Find Any File to search for any files with the application's or the developer's name in the file name.  For CMM software you'd do the following search(es): 


1 - Name contains cleanmymac

2 - Name contains macpaw


Any files that are found can be dragged from the search results window to the Desktop or Trash bin in the Dock for deletion.


FAF can search areas that Spotlight can't like invisible folders, system folders and packages.  


If you get warnings that the file can't be deleted because it is in use or used by another app boot into Safe Mode according to How to use safe mode on your Mac and delete from there.


Note:  if you have a wireless keyboard with rechargeable batteries connect it with its charging cable before booting into Safe Mode.  This makes it act as a wired keyboard as will assure a successful boot into Safe Mode.




Nov 3, 2023 9:18 AM in response to GSF-MF

Translation:

I was almost sure that CleanMyMac was not involved in this matter, but out of conscience, I completely deleted it with the help of Find Any File, as well as AdGuard, so as to have no doubts.


But the problem still persists despite everything.

This is only caused by Safari's iCloud sync.

When the com.apple.Safari.History process is forced to quit, everything is quiet.


From our experiences CMM wasn't helping the matter any.


Give this a try: boot into Safe Mode according to How to use safe mode on your Mac and test to see if the problem persists. Reboot normally and test again.


NOTE 1: Safe Mode boot can take up to 3 - 5 minutes as it's doing the following; 

• Verifies your startup disk and attempts to repair directory issues, if needed

• Loads only required kernel extensions (prevents 3rd party kernel/extensions from loading)

• Prevents Startup Items and Login Items from opening automatically

• Disables user-installed fonts 

• Deletes font caches, kernel cache, and other system cache files


NOTE 2: if you have a wireless keyboard with rechargeable batteries connect it with its charging cable before booting into Safe Mode. This makes it act as a wired keyboard as will insure a successful boot into Safe Mode.


Nov 3, 2023 4:20 AM in response to Old Toad

J'étais presque sûr que CleanMyMac n'était pas en cause dans cette affaire, mais par acquit de conscience, le l'ai totalement supprimé avec l'aide de Find Any File, ainsi qu'AdGuard, afin de n'avoir aucun doute.


Mais le problème persiste toujours malgré tout.

Cela est dû uniquement à la synchronisation iCloud de Safari.

Lorsque le processus com.apple.Safari.History est forcé à quitter, tout est calme.

Nov 4, 2023 7:10 AM in response to GSF-MF

Alors maintenant que faut-il faire pour trouver ce qui cause la saturation mémoire du processus com.apple.Safari.History ? Sachant qu'en mode démarrage sans échec, il n'apparait plus.


Merci encore pour votre aide et merci également pour la découverte de Find Any File, absolument génial !

Très utile pour la désinstallation propre et profonde des App.

Nov 5, 2023 4:36 AM in response to GSF-MF

Depuis aujourd'hui, le démarrage en mode sans échec ne corrige pas le problème, mais en plus, Safari quitte systématiquement !

Safari ne quitte pas avec un démarrage standard


J'ai vraiment essayé toutes sortes d'opérations trouvées sur les forums et autres.

C'est vraiment désespérant de ne pas pouvoir trouver la cause du problème.


La seule chose possible est de quitter le processus com.apple.Safari.History à chaque montage de Safari ou de désactiver la synchronisation iCloud Safari.


Est-ce que quelqu'un a une solution ?

Nov 5, 2023 9:52 AM in response to Old Toad

As of today, starting up in Safe Mode not only doesn't correct the problem, but Safari always quits!

Safari doesn't quit with standard startup...


I've really tried all sorts of operations found on forums and the like.

It's really hopeless not to be able to find the cause of the problem.


The only possible thing is to quit the com.apple.Safari.History process each time Safari is mounted or to disable Safari iCloud synchronization.


Does anyone have a solution?

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Le processus com.apple.Safari.History sature totalement la mémoire et le processeur avec Safari 17.1 sous macOS Ventura 13.6.1 (22G313)

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.