[Solved] Complete Lockup of VirtualBox when using Visual Studio inside guest

[trparky]

I've been able to reproduce this issue multiple times. I go into Visual Studio, search for a string in my source code, press the Enter key several times which should cause Visual Studio to return only one result and then... VirtualBox deadlocks. I can hear audio, the same audio that was sent from the VM guest repeated over and over and over as if the audio subsystem that passes audio from VirtualBox to the host OS locked up. You cannot interact with VirtualBox at all, none of the windows respond. You can't even reset the VM, you have to go to the host system's task manager and kill all VirtualBox associated processes including the system service and restart VirtualBox. Meanwhile the host OS is completely fine and you can continue on as normal.

The host OS is Windows 10 v1809 (17763.316) and the guest OS is the same version.

I have checked the log files from VirtualBox and it appears that whatever is happening the crash of VirtualBox is so deadly to it that it doesn't even write anything to the log file.

[socratis]

and it appears that whatever is happening the crash of VirtualBox is so deadly to it that it doesn't even write anything to the log file.

Are you checking after you've closed the VM process? Could be...

We need to see a complete VBox.log, from a complete VM run, where the problem occurs:

• Start the VM from cold-boot (not from a paused or saved state) / Observe problem / Shutdown the VM (force close it if you have to).
• With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
• Save only the first "VBox.log", ZIP it and attach it to your response. See the "Upload attachment" tab below the reply form.

[trparky]

OK, here it is. I've also been able to recreate the issue using the Windows Sound Control Panel's Sounds tab, selecting an item in the list (for example, Asterisk), and clicking the "Test" button below repeatedly. It appears that the crash is connected to the audio pass-through system.

[mpack]

In that case it's probably a variant on previously reported audio problems. You can try either disabling audio, or using a different simulated audio chipset such as AC'97.

[trparky]

Alright, I just simply disabled audio in the VM seeing that only use the VM to do development in it; I don't need audio in it.

[mpack]

And please confirm that it prevented the lockup?

[trparky]

Well considering that the VM doesn't have an audio card to play audio with one would assume an audio-subsystem related issue would be solved.

[mpack]

That the lockup is audio related was speculation (words like "appears" and "probably" were used), so unless you delved into the code and verified the issue that way then I'd appreciate a straight answer to my straight question. I'm disappointed that I had to ask at all, never mind ask twice.

[trparky]

Since my problem only shows up when I do something stupid, and by stupid I mean do something that would trigger the playback of a sound in rapid succession, and the system locks up at that very point in time I would have to assume (yes, I know what assuming does) that it's an audio subsystem related issue.

[mpack]

Very well. Since you seem unable to answer the question explicitly then I will unilaterally declare the problem as solved. Locking this.