๐Ÿ–ฅ๏ธ rehearsal-mini ยท Rehearsal-Mac-mini.local ยท M4 Pro ยท 48 GB ยท macOS 15.7.4 Probed 18:45 to 19:05 PDT ยท Oct 8, 2026
โœ… Fixed, nothing destructive

๐Ÿ”ฅ Two stuck background apps each pinned one CPU core at 100% for weeks.

Avid Link and UA Mixer Engine were spinning in loops, not doing real work. Both are stopped or restarted. Your Apollo Twin X is still connected.

Both buttons open the Control Room on Greg's Mac.

A chip die with two cores glowing hot

๐ŸงŠ Why Activity Monitor looked calm

๐Ÿ› ๏ธ What was fixed

โœ… Stopped and off at login

Avid Link

  • CPU time: 376 h since boot 20 days ago.
  • Stuck in a menu-bar right-click loop that never ended.
  • Unloaded and disabled for future logins. Pro Tools does not need it to run.
โœ… Restarted

UA Mixer Engine

  • CPU time: 314 h over 20 days.
  • One timer thread spun at 100%. Audio threads were idle.
  • After restart it idles at 15 to 16%, down from 99%. UAD Console reopened.

๐Ÿ“‰ After the fix

ReadingBefore19:08, about 4 min after
๐Ÿ“Š Load average (1 / 5 / 15 min)2.51 / 2.37 / 2.451.15 / 2.07 / 2.33
๐Ÿ’ค CPU idle72.72%88.85%
๐Ÿ‘ค CPU user13.93%2.22%
โš™๏ธ CPU system13.33%8.91%
๐ŸŽš๏ธ UA Mixer Engine99%13.6%
๐Ÿšซ AvidLink99 to 100%Not running, disabled at login Off

๐Ÿ‘€ Left alone, worth knowing

ItemWhat we sawStatus
๐Ÿ“ฆ Dropbox file provider23 GB in memory. A restart brought it back to 22.6 GB in 3 minutes. Memory was 86% free, so no pressure.Your call
๐Ÿ“ก NDI Audio driverHas kept the Mac awake for 355 hours to stream audio over the network. Intentional or not is unknown.Check
โš™๏ธ kernel_task27 h of CPU over 20 days.Normal

๐Ÿ“š Detail

๐Ÿ”ฌ Avid Link, full trace
  • Process AvidLink, PID 533, Intel build running under Rosetta, started at boot.
  • Main thread stack: NSStatusBarButton rightMouseDown, then trackMouse, then _nextEventMatchingEventMask, looping forever. A stuck UI event loop.
  • Fix: launchctl bootout (process gone), then launchctl disable gui/501/com.avid.link.
  • The plist /Library/LaunchAgents/com.avid.avidlink.plist is untouched (RunAtLoad 1, KeepAlive 0).
  • Pro Tools was not running, only its crashpad handlers. Avid Link handles Avid account and updates.
๐Ÿ”ฌ UA Mixer Engine, full trace
  • PID 29994, up 20 days 5 h, 18,857 CPU minutes.
  • The "Socket" thread inside UAD-2 SDK Support spun in boost::asio timer_queue (get_ready_timers, remove_timer). A runaway timer queue, not audio work.
  • Fix: SIGTERM, then launchctl kickstart gui/501/com.uaudio.ua_mixer_engine. New PID 69958.
  • UAD Console quit when the engine went down, with no crash report. Reopened with open -a "UAD Console", new PID 70044.
  • system_profiler still lists the Apollo Twin X. UAD software 11.8.1, UAD Console 1.3.0.
๐Ÿ“ฆ Dropbox and other readings
  • DropboxFileProvider, Dropbox 274.4.4841, account folder Dropbox-RecordingClub.
  • Before: 23 GB resident, 1.5% CPU. Restarted once under the standing order for memory hogs.
  • Within 3 minutes: 70 to 90% CPU rescan, then 22.6 GB physical footprint at 0% CPU.
  • NDI: Core Audio driver NDIAudio holds a "NDI real-time UDP sending" no-sleep assertion, 355 hours.
  • Load average 2.5 before the fixes, 3.1 during the Dropbox rescan.
  • Machine up 20 days 23 h at 18:45 PDT, user tinyroomstudios.
โ†ฉ๏ธ Rollback

Turn Avid Link back on at login, then reopen UAD Console if it is closed:

launchctl enable gui/501/com.avid.link
open -a "UAD Console"

No reboot, no sudo, no files deleted.

๐Ÿšจ What to watch

If the fans ramp up again, run this on the rehearsal Mac and look for UA Mixer Engine or AvidLink near 99%:

top -o cpu

A UA Mixer Engine spike means the timer bug came back. Restart it the same way.

launchctl kickstart -k gui/501/com.uaudio.ua_mixer_engine