Chrome version 76 from the start, on Windows, Mac and Linux platforms run audio separately. Google has been transferred from the audio browser process to a separate process, when the video or audio player in your browser, you can now notice Chrome Task Manager running "utility: audio services."
When the audio system is running in the browser process, if the audio crashes, the whole browser will crash. If the audio hangs, the entire browsing session will be no audio. With this change, the browser will restart the process at the time of the crash audio, seamlessly receive audio, in order to solve the above problems.
To check whether Chrome audio services run in a separate process, start Chrome 76 Stable or later, play any video, press shift on widnows + esc Open chrome in the task manager, you can see utilities: Audio Service tm task to run in.
Google chrome team said it would move to a single platform audio processes of immediate benefit, because the browser process isolation and the audio driver failure, thereby increasing the stability of the browser. Long-term benefit is that the audio processing logic can run in audio processing, that is closer to the hardware, and as far as possible not to transmit the audio buffer to the renderer process, which means a more stable and better audio path delay performance.
Manuscripts: cnBeta