- Blind mode tutorial
lichess.org
Donate

coreaudiod @ 10% cpu on macos firefox

why does lichess burn coreaudiod on macos (firefox) at 10% cpu when not using any audio, including having sounds set to silent? alternatively, what feature/setting can i turn off so coreaudiod is not running in the background when lichess is loaded in the browser?

note that if i close the lichess tab and leave firefox running, coreaudiod returns to ~0% cpu usage.

why does lichess burn coreaudiod on macos (firefox) at 10% cpu when not using any audio, including having sounds set to silent? alternatively, what feature/setting can i turn off so coreaudiod is not running in the background when lichess is loaded in the browser? note that if i close the lichess tab and leave firefox running, coreaudiod returns to ~0% cpu usage.

This is what happens when an application plays sound on a Mac these days. Audio playback incurs a certain amount of fixed overhead with built-in mixers and EQ but I suspect most of that CPU is likely ambient noise reduction for mics. If you happen to have an Intel mac without a T2 chip you can disable ambient noise reduction in System Settings. That might help. Try plugging some headphones into the lineout and see if it cuts that usage in half, if so that's ambient noise reduction.

The gold standard solution is to stop watching Activity Monitor. Good news is that it's fixed overhead (the amount does not increase by 10% for every app that has an open coreaudio context).

This is what happens when an application plays sound on a Mac these days. Audio playback incurs a certain amount of fixed overhead with built-in mixers and EQ but I suspect most of that CPU is likely ambient noise reduction for mics. If you happen to have an Intel mac without a T2 chip you can disable ambient noise reduction in System Settings. That might help. Try plugging some headphones into the lineout and see if it cuts that usage in half, if so that's ambient noise reduction. The gold standard solution is to stop watching Activity Monitor. Good news is that it's _fixed_ overhead (the amount does not increase by 10% for every app that has an open coreaudio context).

This topic has been archived and can no longer be replied to.