"audio engine is NOT running" - edit: possible trigger for this message determined.

[peterthegrey]

I run BeebEmBeta4 by double clicking on */BeebEm/Contents/MacOS/BeebEm and therefore see a monitoring window in the Terminal app.

When doing one of several common operations - pressing BREAK in some form, adding a second Processor, even sometimes changing the base machine, I get the message
"audio engine is NOT running"
appearing repeatedly and at a fast rate until the instance is terminated.

This does not appear when the instance is started, or by eg mounting a floppy disc, getting a directory listing and suchlike.

While it does not appear to be affecting other things running in the emulator, it seems odd.

[peterthegrey]

I think I was wrong about there being no effect to this issue. I left 4 instances running in an emulated ECONET config for several hours, and the memory use of the instances went up to as much as 14GB in that time. I am not sure how to check/investigate where such a memory leakage is coming from.

[peterthegrey]

I have been seeing this issue every day, until today. I have not been able to trigger the message at all. I do not believe I have done anything with app permissions, with the underlying macOS, with the other software running on the Mac at the same time. I am baffled. I will continue to try to identify what the trigger to this behaviour might be. Please don't spend a lot of time on this if you cannot immediately replicate it.

[peterthegrey]

I have found one trigger at least. I had an AirPod in so as not to disturb others. Took the AirPod out and the message started. Simply turning sound on and off does not do it, but changing the sound destination does. I'm puzzled though, as that is not an action that I remember taking where it was triggering every time previously.