Crash on audio device switch

[allenb]

I am running VirtualBox 7.0.12, Win 10 host, Ubuntu guest.

I was listening to audio from my Ubuntu VM when I accidentally powered off my bluetooth headphones. I powered them back on and thanks to the recent patch for #20431, they resumed playing audio within a few seconds (yay!). Less than a minute later, I got an error message from Windows "the instruction at XX tried to access memory at address YY, the memory could not be written". I moved the error dialog out of the way and the VM appeared to operate normally, with audio still playing and programs functioning. After about an hour, though, it got so unstable that I had to click "OK" on the dialog and force-close the VM.

I have experienced this crash multiple times since the patch for the audio switching issue was applied. The sequence of events is always the same: audio device disconnects, then reconnects, wait a few seconds, then error. I originally observed it in the test build that pentagonik posted to ticket #20431, but figured it was just part of the instability of a nightly build. However, this is now the third time that I've experienced this crash with the release version 7.0.12.

A log file is attached. The headphones disconnect on line 1715, reconnect on line 1746, and the exception/crash (with stack trace) starts on line 1805.

[allenb]

Log showing crash at line 1805

[kishi]

I'm running into this crash (similar logs) as well and can pretty much realibly trigger it by connecting and/or disconnecting to a remote desktop session on the machine running VirtualBox using Sunshine (​https://github.com/LizardByte/Sunshine) and Moonlight with the Host Mute Option enabled so that Sunshine switches to and from the "Steam Streaming Speaker" Virtual Output.

The crash does not occur when audio is disabled on the guest or (what i've done for now) downgrading to 7.0.10, which most likely means that something in the new WAS Audio code introduced in 7.0.12 seems to cause the issue.

[pentagonik]

Duplicate of #21931.