SafariDAVClient Sucks Up RAM and Does Nothing Useful

It’s enough that Safari itself sometimes uses a huge amount of RAM, along with the WebProcess process, but another Safari-related process, SafariDAVClient is an even bigger memory hog. Currently, on my Mac mini which has 8 GB RAM, it is using 1.36 GB real memory. (Screenshot taken from a display provided by iStat Menus.) I have seen this process go well over 2 GB, yet it does nothing useful.

It is supposed to be used to sync bookmarks via iCloud, but in my case, the syncing doesn’t occur. I’ve tried turning off and on bookmark syncing to no avail, and have gotten to the point where I transfer my Safari bookmarks file from my Mac mini to my MacBook Air from time to time. It’s even worse with my iOS devices, as bookmarks simply won’t sync to them at all.

I guess I should simply turn off bookmark syncing, as it seems to be a total failure. Unless any of my readers have a trick to get it to work…

Posted: 1/16/2012 by | Filed under: Apple & Mac OS X | 3 Comments »
Take Control of iTunes 10: The FAQ, Second Edition


3 Responses to “SafariDAVClient Sucks Up RAM and Does Nothing Useful”

  1. Nikolozi says:

    I’ve had similar experiences with those Safari related processes hogging up RAM/CPU and bookmark syncing not working properly.

    I love Reading List feature but I’ve stopped using as it never sync-ed properly. Removed items wouldn’t remove from all devices. So I had to delete read items multiple times…

    I’m trying hard not to switch back to Chrome.

  2. Michael says:

    Well folks – I have given up on Safari and gone back to Chrome. What’s the point of paying extra $$’s to boost memory to 4GB on my MacBook Air if Safari is using it as if there is no tomorrow…

    • Aaron says:

      I’ve done the same. Chrome can handle dozens of tabs open at once with no problem. In Safari, just a few tabs causes it to hang. Unfortunately, Chrome doesn’t support RSS, so I still have to switch to Safari occasionally.

      There’s also a few caveats of Cocoa features that Chrome doesn’t fully support yet, like autocorrect.

Leave a Reply