DFRHUD and TouchBarServer high CPU when idle
I noticed my laptop fan would start spinning when the laptop is sitting idle (and connected to an external monitor).
It happens pretty reliably.
If the computer is in use, everything normal.
If i stop using it, for a few minutes everything is normal.
Then after about 10 minutes the fan starts spinning, as if some process is doing a lot of work.
If i unlock/wake the screen, Activity Monitor shows there was indeed high CPU usage, however it stopped the moment i woke the computer up.
i.e. the 'busy' process goes back to idle as soon as i touch the computer.
To figure out which process is hogging the CPU (since Activity Monitor isn't helping):
# Print the top 10 processes by CPU usage (and other stats) every minute
while true; do echo; date; iostat; ps -c '-O %cpu %mem' |head -n 1; ps -c -A '-O %cpu %mem' | sort -r -n -k 2 | head -n 10; sleep 60; done
Example output (taken when the computer is awake):
Wed Apr 1 10:16:38 PDT 2020
disk0 cpu load average
KB/t tps MB/s us sy id 1m 5m 15m
68.05 121 8.05 17 10 73 3.57 7.86 9.43
PID %CPU %MEM TT STAT TIME COMMAND
58613 19.7 0.2 ?? S 0:45.92 appstoreagent
495 18.3 0.1 ?? S 3:50.37 nsurlsessiond
1683 13.7 2.1 ?? S 108:57.87 iTerm2
255 11.9 0.9 ?? Ss 789:08.68 WindowServer
46138 8.3 0.4 ?? S 0:19.50 AppleSpell
59730 8.0 5.8 ?? S 1:26.49 java
1474 5.1 1.1 ?? S 175:49.99 Google Chrome
58187 4.1 1.1 ?? S 0:26.67 Google Chrome Helper (Renderer)
57406 4.0 0.4 ?? S 110:45.12 Atom
57424 2.2 0.1 ?? S 23:28.52 Atom Helper
I've been running this for a few days now, and whenever i notice the computer idle and fan spinning, i unlock and take a look at what's going on.
There are 2 processes consistently using elevated CPU during idle time:
DFRHUD and TouchBarServer.
They never seem to use any CPU when the computer is wake/active.
However 10 or so minute after it goes idle, both processes spin up and use 30-70% CPU for as long as the laptop is idle.
I tried killing both. They soon re-appear, and exhibit the same behavior.
I found very little information online about either of them.
Can someone shed some light on:
- What they are / what they do
- Whether this is a bug or part of some background / idle service, or worse, cleverly disguised malware
Any info appreciated.
MacBook Pro