cfprefsd is hijacking my CPU

[Nico1961]

Suddenly a process named ”cfprefsd” takes up about 75% of CPU.
It's impossible to quit it.
Even when force quitting in Activity Monitor, it just starts back up again within seconds.

Anyone has advice on this it will be greatly appreciated
Peter

 

[mrplow]

Welcome to the forums.

Open Activity Moniter.
Make a note of the PID for cfprefsd

Open Terminal and enter
sudo fs_usage pid xxxxxx

where xxxxxx is the noted PID

This will tell you what vfpresd is writing to.

Post back with the results

 

[Nico1961]

Thanx for your reply.

I got an endless amount/list of info in the terminal window, starting like this:

Last login: Wed Nov 29 08:33:19 on ttys000
Peters-iMac:~ peternicolaisen$ sudo fs_usage pid 1666
Password:
09:58:02 open /.GlobalPreferences.plist 0.000017 cfprefsd
09:58:02 fstat64 0.000002 cfprefsd
09:58:02 open 7-96F4-94E2A4456CAE.plist 0.000035 cfprefsd
09:58:02 read 0.000010 cfprefsd
09:58:02 read 0.000001 cfprefsd
09:58:02 HFS_update 0.000001 cfprefsd
09:58:02 HFS_update 0.000001 cfprefsd
09:58:02 close 0.000006 cfprefsd
09:58:02 open ple.SpotlightServer.plist 0.000040 cfprefsd
09:58:02 open 7-96F4-94E2A4456CAE.plist 0.000029 cfprefsd
09:58:02 open references/mdworker.plist 0.000020 cfprefsd
09:58:06 open .Extensions.plist.sfkgiLZ 0.000033 cfprefsd
09:58:06 fcntl 0.000006 cfprefsd
09:58:06 HFS_update .Extensions.plist.sfkgiLZ 0.000009 cfprefsd

 

[Nico1961]

Looks in Activity Monitor like it has something to do with "Blued". Don't know what that is, though. Or how to close it down.

 

[mrplow]

I can't see BlueD in the exercpt you've posted but that's your bluetooth daemon.

You don't say which Mac you're on. Provide you don't rely on Bluetooth for your keyboard and mouse/trackpad turn Bluetooth off and see if that affects your CPU usage.

If you can't turn Bluetooth off go to /Library/Preferences/ and delete all instances of com.apple.Bluetooth.plist

Reboot and check

 

[Nico1961]

I'll try your suggestions, thanx.

 

[Nico1961]

Now it's gone, thanx.
Hope it stays that way

 

[mrplow]

OK good.

Somethings the bluetooth stack can get 'stuck' or 'corrupt' on upgrade. Hopefully that'll sort the issue for good.