logd high cpu

srand06 wrote:

Hi,

what is /usr/libexec/logd process ? It's consuming a high percentage of CPU :

I have killed notification center:

sudo killall -9 NotificationCenter

And also Google Chrome Helper and immediately dropped to 5% CPU usage.

For me this happened when i opened Google Chrome Browser (MacOs Sierra 10.12.2 / 16C67).

After i closed Google Chrome, the problem went away.

So it seems that a GoogleChrome process (website) caused the problem.

Hope it helps.

same here

I have the same problem...

I have this problem too. I'm not using any applications or undertaking any tasks, and logd is using over 100% of CPU...

Only been happening since I've upgraded to Sierra 10.12, running mid 2012 Macbook Pro, 2.6 Ghz i7, 8 GM ram

I also have this periodic runaway logd process. I noticed that it would often happen if a backup got stuck on the verification stage. Maybe just a coincidence but it's very annoying.

Has this happened again since your post?

Yes, it happened to me again 2 days ago ...

i got also a machine like that. i installed last week the sierra. today i realized the constant over 140% logd activity. Also when i **** down all programs it is like that. what is to do? waiting like some are writing?

Samesies. Happened a couple of times. Just now I was watching the CPU and shutting down apps one at a time, give things time to settle after each app closing, and killing Chrome Beta removed logd and it's CPU cycles.

I opened Chrome again and boom, logd was back and taking up 100% CPU. I only had about 6 tabs open, so I opened up task manager in Chrome and my google sheets were the culprit. I had three of them open. I closed them and logd dropped off again.

So in this instance, I narrowed it down to Google Sheets in Chrome Beta causing the logd issue. Running 10.12.1 on a 12" Macbook early 2016, 1.3Ghz Core m7.

Did anyone find a way to stop it without rebooting ? I tried to kill it but it restarts automatically, and when it runs, my poor MBA can't do anything else without being slow as a snail !

I also face the same issue very frequently after updating the MacOS Sierra on my 2014 MacBook Air. Apply or anyone please help.

Best,

Experienced this problem today with Sierra 10.12.1 on my MacBook Pro (Retina, 15-inch, Mid 2015)

Had to restart my MBP to fix the problem.