fatal error: unexpected signal during runtime execution about portaudio

[gordonklaus]

At first glance I see that there is no synchronization around Audio.fanOut. You might want to run with the race detector enabled to see if there any other such issues.

Also, are you sure Audio.Wait should call Audio.start? It seems like the stream ought to be started only once, and Wait should only sign up listeners.

[aklinkert]

Right, that code was meant to be used like that, but reality came different. :) Right now this code around the notify logic is sonewhat overengineered due to history, but stable, as only one process / routine / method ever calls the audio.Wait method. The audio reading could indeed run in the background, but I don‘t see the necessarity as I need the aufio informstion only once every few minutes, so I personally find it more efficient to start the stream when needed.

[aklinkert]

So, assuming that the audio.go code is working as expected, any other suggestions regarding the portaudio error? 🤔 😐

[gordonklaus]

only one process / routine / method ever calls the audio.Wait method.

Regardless, in the output you posted I see many goroutines in Audio.notifyWait (which is only reachable from Audio.Wait). There is concurrency going on there without synchronization. Either you need to use a mutex around Audio.fanOut or you need to make sure those Audio.readStream goroutines exit before you return from Audio.Wait.