Love to see Beep being used! Your game looks cool!

From only the stack trace I can only make some guesses to what's happening:

1. Some concurrency error. Make sure that when you make changes to the Mixer (Add or Clear) that you Lock the speaker. See the tutorial.
2. I see that one Mixer is used by another. Make sure the Mixer isn't consuming itself.

If that doesn't help, I would appreciate if you could share some code so we can further debug the problem.

Thanks for the quick reply! The problem was due to locking. For some reason (I can no longer remember) I was using my own mutex instead of speaker.Lock(). Switching to locking/unlocking via the speaker fixed the problem. Thanks again!

One last point: this issue is still happening but far less frequently now. Specifically, it seems to be related to calling mixer.Clear() from inside a Callback. According to the source, speaker is locked during a callback so I'm not calling speaker.Lock() here. (Calling it caused a deadlock, which makes sense.)

I think maybe the issue is that I try to clear() the mixer after a sequence has finished playing. In faiface/beep I had to do this but maybe finished streamers are automatically removed in this version?

I've made a PR to check whether the mixer has been cleared during streaming to prevent the panic.

Both faiface's implementation and ours remove streamers which are done playing but our version is a bit more aggressive about it and removes them when they return less than the requested samples instead of waiting for the !ok signal that has to follow it. This doesn't entirely explain the panic but it's possible that you don't need the clear for your use case.

Yes my "fix" was to not clear the mixer after the sequence is done. This eliminated the crashes, I was just curious if it will lead to a memory leak. Thanks for looking into this!

Ps.: I can also post the audio code in a github gist but I didn't want to saddle you with debugging my code. If you want to see it though, let me know.

I think we tackled the problem so it's just out of curiosity. If it isn't a hassle, please share :)

Also, blind debugging is more difficult than with a small reproduction snippet.

Here is the audio code for enalim. Please don't judge, I'm a total n00b in audio coding... If you have suggestions for improvement, please let me know!

Enalim plays:

• music (changes by day/night, location, combat)
• ambient audio (fireplace, fountain, etc.)
• environmental audio (rain, wind)
• sound effects in two channels: short (doors, attacks, etc.) and longer (level up, death, etc.)

Most of the game is implemented in script, which makes calls to (for example) audio.Play(). Because it's an opengl game, all of this is single-threaded.

https://gist.github.com/uzudil/5091f7d4ef55cd6ae5bc5b78bba44cf7

Also, if you want, I can give you access to the full game source.

I forgot to add: the previous version (where the crash happened, used to call audio.Music.mixer.Clear() from the Callback on line 439.

One more comment: audio.updateMusic() is called from the main game loop to handle fading between various musics. (eg. if combat breaks out, we fade to the combat music.)