virtualbox.org

---

ModEdit; related ticket: #18916: VRDP enabled, clicking repeatedly on the sound level freezes WinVM/VirtualBox Manager

---

Since I moved from VB 5.2 to 6 (first the beta versions, then 6.0.0, now 6.0.2 r128162, my Windows 7 client freezes very often.

It seems that the problem occurs whenever a windows dialog appears, e.g. when a remote desktop inside the client says that the connection is lost, or in Total Commander when a "diff" says that there are no differences found.
I have collected the logs of several occasions. Can anyone give me a hint what's happening here? Should I go back to VB 5.2?

Additional information: my host is windows 10, 1809, Build 17763.253
The frozen guest takes 100% cpu time and does not react on anything any more, even for several hours
I can only kill the guest window, nothing else works

Thanks for any help!

I downgraded to 5.2.26 and the freezes do not occur any more.

seems to be a major problem with 6.0. Can anyone help?

I have the same problem and also downgraded to version 5.

Same here, it seems to be a general problem with sound.

Steps to reproduce:

• Install WinXP.
• Install Guest Addons.
• Use Audio "Windows DirectSound"
• Use Audio Controller "ICH AC97"
• Open in the right corner the sound, click several times on the volume control so it plings several times - the machine is crashing massive, you can only close window.
• Even VirtualBox.exe (VBox Main Window) is sometimes freezing.

This explains why it happens with dialogs - they play sound.
I will try without audio for some time.

Ok, further tests revealed that it has not directly something to do with sound.
It is a problem with REMOTE CONTROL.

Host:
Windows 10 RS5 x64, all updates installed (several different hosts)

Tested guest systems:
Windows XP x86 SP3
Windows 7 x64 SP2

VBox Version: 6.0.6 r130049

Steps to reproduce:

• Install a fresh system with default settings or use an existing system
• install guest additions (not needed to reproduce on my side)
• Shutdown system
• Enable remote control in machine settings under display (Serverport: 3389 or other; Authentication: Null; Timeout: 5000)
• Start system
• click in volume control panel the volume rocker several times (at least 20) so you can hear the "pling" sound

Voila: Guest System is freezing / crashing and even VBox Manager freezes till system is force closed!
This needs definately to be fixed.

PS: It is not needed to remote access the machine.

Can someone confirm?

JayEm yes I can confirm. In fact, you're kind of my savior! I was just getting ready to post a bug report related to this; for me this has been extremely annoying as I have enabled remote control on all my VMs - just because there was an option to do so ...

This bug manifests itself if:

• VirtualBox version is 6.0.4 or 6.0.6 (haven't tested older versions)
• remote control is enabled
• 'Audio output' is enabled (AFAIR even if 'Host Audio Driver' is set to 'Null Audio Driver')
• tested for both 'Intel HD Audio' (for Win7 VM) and 'ICH AC97' (for WinXP VM) set as 'Audio Controller'

on the following x64 hosts:

1. Win7 Ultimate, fully updated
2. Win7 Professional, not updated for a year
3. Linux Mint 19.1, fully updated <-- so not only for Windows hosts!

on the following guests:

1. Win7 Professional 64-bit
2. WinXP SP3 32-bit

Clicking a few times at volume control in the Windows guest is enough to hang the whole VirtualBox.

Linux guests (at least Linux Mint guests) seem to be immune to this problem.

Disabling 'Audio output' helps, but the option to turn off Remote Control is a far better workaround for now, thanks again JayEm!

NOT fixed in 6.0.8
Tested on W7 x64 host & guest

After disabling Audio, it seemed solved at my system.
To be sure I also disabled Remote Control, seems to be stable now.

Disabling Audio seems to solve the problem also, but enabling null audio driver doesn't solve it. So i believe the real cause is the remote control option where the bug lies.
Disabling Audio simply circuvments the bug in remote control.

Hello,

agree same issue here.
Windows 7 64 Bit host system (Dell Laltitude E5470), Windows Audio driver is the most recent.

I already tried 5.2.18, 5.2.20, 5.2.22, 5.2.24, 5.2.26, 5.2.28, 5.2.30, 6.0.4, 6.0.6, 6.0.8

I tried Ubuntu, Fedora, Arch Linux

For me the issue appears when selecting INTEL HD or ICH97 with DirectSound.
With Arch linux I disabled boot into GUI - just by command line entry "aplay Sample.mp3" the system crashes - "CPU 1 hang" messages appear on console and in VBox.log there are messages: Client is unresponable for X seconds.
Only help way to stop it is to turn hard off VM from main window.

With Null Audio driver selected there is no issue for me.

Earlier this configuration was working.

Please solve this issue, I want to have sound inside the VM.

Best regards

Kitsab

Observed with XP host running audacity which will freeze the program (audacity) and disable audio, either immediately or after some period of time.

VB Version 6.0.8 r130520 (Qt5.6.1) on Xubuntu, 16.04

NOT fixed in 6.0.10
Tested on W7 x64 host & guest

Is this bug really low priority?

msys wrote:Is this bug really low priority?

I agree. This is a real show stopper bug.

Still existent in 6.0.12.

Sound like you guys are having quite a problem! Unfortunately we here are just fellow users, and not the developers.

msys wrote:I was just getting ready to post a bug report related to this

Did anyone here actually do this? That's the only way to get the devs' attention. Otherwise "me-too-ers" are just preaching to the choir.

If someone did post or find a Bugtracker ticket they should be able to post a link here so folks with this problem can go to the right place to check up on it or contribute to a solution. Especially as there's apparently repeatable steps to make the problem happen.