Google will have a separate audio process on Chrome starting from Chrome v76. The Chrome version 76.0.3809.87 for Windows, Mac, and Linux will now run Audio in a separate process that will allow Chrome to control the process separately.
Earlier, in Google Chrome, the audio process was not a separate process which would often result in whole browser crash in a single crash or glitch in audio. With this new processor, Chrome will be able to restart it even if the audio process causes some issues.
To see how the change is effective. Just open any audio like website e.g. YouTube or Amazon Music and press Shift+Esc to open Chrome’s Task Manager and search Audio service in the task manager. It seems that finally, the bug for Chrome v76 is closed and fixed today.
The immediate benefit of moving platform audio to a separate process has increased browser stability due to isolating the browser process from audio driver faults.
The long-term benefit is enabling audio processing logic (such as echo cancellation) to be run in the audio process, i.e. closer to the hardware and without passing audio buffers to renderer processes wherever possible, which means having a more stable audio path latency and better performance (we can better tweak priority of the audio process as well).
Chrome v76 update is already available for Windows, Mac, and Linux platform and will install automatically.