'ubd' process huge cpu load

I am having this exact same issue, and I think it is causing certain apps (perhaps ones with a potential link to iCloud) to hang upon opening. UBD is continuously sucking between 60-99% of my CPU usage. I can't even open Keychain Access to check on one of these suggestions.

I think you may can just delete "ubd" from => /System/Library/PrivateFrameworks/Ubiquity.framework/Versions/A/Support/ubd

I did it. It`s working for me. But I don`t know if any problem may happen because ubd was killed.

So I backup "ubd" prevent I need it again... : )

good luck

Seems the best solution for me, I'll try the same as I don't have any "com.apple.ubiquity.*" certificate

Try the following:

- open your Keychain

- search for items with 'peer-uuid' in their name

- if there are a lot and you notice that their amount is growing then

- lock your session keychain

- select all items containing such 'peer-uuid' string in their name and delete them

Then

1/ drag your Preferences Folder to the desktop

2/ close your session

3/ reopen your session

The problem shall be gone

I tried the above suggestion to no avail. I had this pop up only under 1 of 2 managed accounts. I logged out the user, then logged the user back in. When I did that I received a keychain popup asking for the keychain password, or create a new keychain.

Once I hit, "Create New Keychain", then logged in, the pop up stopped.

Hope this helps someone

Just a note that the solution of diglin, changing the owner of the folder Ubiquity from root, immediately worked for me.

I had just configured a new Mac Pro, by dragging my user folder from a circa 2008 core duo Mac Pro that already had Lion on it. Before the fix ubd was a constant 99% of cpu.

Thanks to all of your post, I found the problem. the rights of the folder ~/Library/Application Support/Ubiquity/ was incorrect. The owner was the root, I change it to me. After the ubd process manage to create content inside of it.

I think you may can just delete "ubd" from =>/System/Library/PrivateFrameworks/Ubiquity.framework/Versions/A/Support/ubd

I did it. It`s working for me. But I don`t know if any problem may happen because ubd was killed.

So I backup "ubd" prevent I need it again... : )

I have found that while going to the ~/Library/Application Support/Ubiquity/ directory and yes changing it from root to another user, you can also lock that file down, or folder.

You can delete the contents in ~/Library/Application Support/Ubiquity/ before using secure delete, then locking it down.

I did also delete the ubd file in /System/Library/PrivateFrameworks/Ubiquity.framework/Versions/A/Support/ubd

dire and changed the user to no access or read only. Alwase back up something your not sure you should delete.

Then going into keychain again Deleteing the untrusted certificates, change the settings to Lockdown.

So far so good...

To think like a hacker is the only way to defend against a hacker. They though have the intent to do so.

I am now learning the Directory Utility and each reference it has and what it should look like.

Surprised as I am I didnt even think about researching ubd or the unknown or ect before doing any of this, its quick and painless, and it seems good that the RED x is just not there.

This is what worked for me... hope it helps...

This should be done on all user accounts.

Think the best way is to trust yourself in what would work best, I took the best workarounds on this thread and on others, reseached tech meanings, and trusted.

Why you feel this way about it is the reason for thier intent. Empty.

Thanks for your post. This was the solution for me.

I just opened the Terminal and changed the directory to Application Support with:

cd Library/Application\ Support/

I listed the content of the directory with the command:

ls -l

and then I saw that the directory Ubiquity was owned by the user 'root' with the group 'admin':

drwxr-xr-x@ 7 root admin 238 14 Jan 10:11 Ubiquity

With the following command I changed the owner of the direcotry to myself:

sudo chown donbilbo:admin Ubiquity

Notice that you have to replace donbilbo with your own username! The sudo is needed because you change the owner from root to yourself. After typing in a command with sudo you have to enter your passwort to get system privilegs to change a directory which is owned by root.

After changing the owner of the directory the ubd process just added 1 key to the keychain and the ubd process is ok with 0.1 percent cpu load.

Big thanks to diglin!

Muchas , pero Muchas gracias!! , esta falla me tenía muy preocupado, pero efectivamente ingresando a Acceso a llaveros , luego Preferencias de Acceso a llaveros y restaurando en la pestaña General

"Restaurar mi llavero por omisión"

hamster116 wrote:

I found that my keychain is a mess, it contained around 1600 items starting with com.apple.ubiquity.

Cleaning up the items was impossible until I locked my keychain, but upon unlocking ubd started adding new items again.

I just found a fix, though. There is a certificate (not a key) in my keychain called 'com.apple.ubiquity.peer-uuid", which was marked as untrusted. I opened it's info dialog and set it to "always trust". That seemed to work, although I do not know if there is other implications for me doing that. Now the ubd proces is still active, but runs at a nice 0.0% CPU.

I also went to the keychain preferences and clicked "reset my default keychain", this might have helped fix it as well, but I think it's the certificate thing.

Hope this helps!

ENG.

Greetings I have made your recommendations and the fault persists, ubd is swallowed processor performance.
If you have any suggestions I appreciate it.

Sampling process 698 for 3 seconds with 1 millisecond of run time between samples

Sampling completed, processing symbols...

Analysis of sampling ubd (pid 698) every 1 millisecond

Process: ubd [698]

Path: /System/Library/PrivateFrameworks/Ubiquity.framework/Versions/A/Support/ubd

Load Address: 0x102de2000

Identifier: ubd

Version: ??? (???)

Code Type: X86-64 (Native)

Parent Process: launchd [225]

Date/Time: 2012-01-20 09:33:01.350 -0500

OS Version: Mac OS X 10.7.2 (11C74)

Report Version: 7

gonzalogabriel

ESP.

Saludos he realizado tus recomendaciones y la falla persiste, ubd se traga el rendimiento del procesador.

Si tienes alguna sugerencia te lo agradezco.

gonzalogabriel

Hello gonzalogabriel,

you also have to clean your keychain, because it's possible that the ubd process will cause a high cpu load when your keychain is full of thousands of keys and the process tries to add another one.

I think the best method is to turn off iCloud, then clean your keychain and the turn iCloud on again.

Hope this helps.

Thanks for the tips (thanks to everyone, actually!).

What do we do with the preferences folder we dragged to our desktop once we've reopened the session?

Thank you again

I started out with four of them that showed up, and then this afternoon almost 3000 were added! I created a new key chain and deleted that one because it wouldn't allow me to just delete those specific entries.

Hi there,

Just wanted to chime in I had the same issues with the massive CPU usage that was illustrated in the ubiquity.log in the Console. My process was given as 'securityd' in Activity Monitor.

At the moment, I've stopped the process from starting up by moving the /Library/Preferences in my user folder out and then restarting.

From there, I'm going to move back in all non-"com.apple.*" related preferences since this seems to be MobileMe->iCloud related. I will then incrementally add in Apple-related preferences into the folder again and see if I can nail down the offending file.