Virtualbox 6.0.2 audio causing a crash

[gaogeli]

host is arch, newest kernel. guest os is win10 x64.
if audio enabled and playing some music, the vm will crash within a few minutes.
dmesg show "EMT-1[6789]: segfault at 7f1b188e3f74 ip 00007f1b47af0cf8 sp 00007f1b189e28e8 error 4 in libc-2.28.so[7f1b479b3000+14b000]".
if audio disabled, every things is ok.

[gaogeli]

It seems that the microphone device is disabled and the system will not crashing.

[06b7e]

My problems seems related. Virtualbox Version 6.0.4 r128413. Host is Ubuntu 18.10 and guest os is Windows 10 x64. VM is crashing within 2-4 minutes after starting if audio is enabled.
Reproduced on Ubuntu 19.04 (daily build), with disabled/enabled microphone on either BIOS or software. Audio controller does not matter.
The issue is solved by disabling audio or using "null driver audio". In any case, the sound in guest does not work (which is not acceptable long-term).

Log says:

Code: Select all

EMT-3[9451]: segfault at 7f15202f6fb4 ip 00007f1544c22594 sp 00007f15203f58c8 error 4 in libc-2.29.so[7f1544abe000+173000]
Code: 0e 88 0f c3 c5 fa 6f 06 c5 fa 6f 4c 16 f0 c5 fa 7f 07 c5 fa 7f 4c 17 f0 c3 48 8b 4c 16 f8 48 8b 36 48 89 4c 17 f8 48 89 37 c3 <8b> 4c 16 fc 8b 36 89 4c 17 fc 89 37 c3 0f b7 4c 16 fe 0f b7 36 66

No relevant log in virtualbox or windows event viewer.

[fossanico]

Same problem here.
Virtual Machine crashes and shows up as interrupted after playing audio for some minutes.
Host Arch Linux, Virtual Box 6.0.8 r130347, host Windows 10 x64 latest update
The KDE debugger also crashes, so I cannot get debug information

The problem was present even with older releases of Virtual Box

[kernelpanic]

I'm also experiencing this very irritating issue on the latest Arch kernel, VirtualBox 6.0.8 r130347, with a Windows x64 guest with Guest Additions installed. In some programs, like FCEUX, the audio is completely gone, until a couple minutes later, where I hear a short bit of static, then the VM closes.

[socratis]

@ALL
When there's a problem, the developers 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.