I have OverSight installed on my macbook (https://objective-see.com/products/oversight.html), which lets me see which apps activate the microphone.
Up until now, everything was quiet and expected.
As of today though, Chrome (Version 78.0.3904.70) tried on several occasions to activate the microphone. It crashed when I denied the request. I have not been on any website requiring microphone use and no website is allowed microphone access.
This seems to happen in particular when I reopen the lid of my macbook and it is taken out of sleep.
This is the log entry from OverSight:
2019-10-31 19:27:22 +0000: Audio Device became active (Built-in Microphone, process: Chrome Helper, /Applications/Google Chrome.app/Contents/Frameworks/Google Chrome Framework.framework/Versions/78.0.3904.70/Helpers/Google Chrome Helper.app/Contents/MacOS/Google Chrome Helper)
Any of you noticed a similar behavior?
I wouldn't be surprised if this is intentional, surreptitious behavior. Regardless, Firefox is excellent and Chromium is an OK fallback when you (rarely) need it.
I don't know if web workers allow microphone access but, in case you've allowed a website to access your microphone recently, I'd check if it hasn't installed anything automatically they could be triggering this.
It could be Chrome is just checking the device configuration for input/output at the same time (it needs the latter for the audio APIs) and the service might be pinging that as "microphone activity" when really they're just checking the available devices and their settings.