Vbox WinOnWin over RemoteDesktop unattended crash

[PHolder]

I run a Windows 10 (22H2 fully updated and patched) machine remotely. It has the latest VirtualBox (7.0.12.9484) installed. I launch a vm also running a fully patched and up to date Windows 22H2 with the add-on installed. (I doubt the use of the vm itself is important to the problem, but in that machine I launch qBittorrent and leave it running doing its thing, reading/writing to a shared folder mapped to drive T: in the vm.)

For many versions of VirtualBox I have been experiencing two different problems, which I have been hoping against hope would get fixed by updates to VirtualBox:

1. One, the VirtualBox manager UI, which I left running, randomly exits with no warning (but always when the machine is unattended, with the remote session still running, but minimized on the originating machine. The VirtualBox host will lock the screen, and require a password login to reconnect, and when I unlock, the VirtualBox manager UI is no longer running.)

2. Infrequently, the vm will appear to hang. I can still work with the chrome on the Windows, so I can try to send in C-A-D or choose to send various other inputs, but the machine in the window no longer responds. My only recovery is to power off the virtual machine, and then relaunch it and hope the unclean power down didn't cause havoc.

Because of these two different issues, I have been installing each update to VirtualBox as soon as they come out. This is how I have 7.0.12 now installed.

While the machine was unattended last night, it did something new. When I brought up the Remote Desktop window, it was sitting waiting for a password, but on top of that window/screen was a crash report dialog.

---------------------------
VirtualBoxVM.exe - Application Error
---------------------------
The instruction at 0x00007FFF8DA26DB2 referenced memory at 0xFFFFFFFFFFFFFFFF. The memory could not be read.


Click on OK to terminate the program
Click on CANCEL to debug the program
---------------------------
OK Cancel
---------------------------

I looked in the Reliability Monitor and found:

Faulting application name: VirtualBox.exe, version: 7.0.12.9484, time stamp: 0x652832d4
Faulting module name: Qt5GuiVBox.dll, version: 5.15.2.0, time stamp: 0x606c96f9
Exception code: 0xc0000005
Fault offset: 0x0000000000066dc8
Faulting process id: 0x2114
Faulting application start time: 0x01da017891b694a7
Faulting application path: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
Faulting module path: C:\Program Files\Oracle\VirtualBox\Qt5GuiVBox.dll

[fth0]

Please provide a zip file with the contents of the VirtualBox global configuration folder (C:\Users\<username>\.VirtualBox). Additionally, please provide a zip file with the VBox.log* files of the VM.

[PHolder]

It just happened again last night, attached are the requested logs

---------------------------
VirtualBoxVM.exe - Application Error
---------------------------
The instruction at 0x00007FFBD7366DB2 referenced memory at 0xFFFFFFFFFFFFFFFF. The memory could not be read.


Click on OK to terminate the program
Click on CANCEL to debug the program
---------------------------
OK Cancel
---------------------------


Faulting application name: VirtualBox.exe, version: 7.0.12.9484, time stamp: 0x652832d4
Faulting module name: Qt5GuiVBox.dll, version: 5.15.2.0, time stamp: 0x606c96f9
Exception code: 0xc0000005
Fault offset: 0x0000000000066dc8
Faulting process id: 0x1ae8
Faulting application start time: 0x01da04a85859b7f5
Faulting application path: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
Faulting module path: C:\Program Files\Oracle\VirtualBox\Qt5GuiVBox.dll



Faulting application name: VirtualBox.exe, version: 7.0.12.9484, time stamp: 0x652832d4
Faulting module name: Qt5GuiVBox.dll, version: 5.15.2.0, time stamp: 0x606c96f9
Exception code: 0xc0000005
Fault offset: 0x0000000000066dc8
Faulting process id: 0x1b78
Faulting application start time: 0x01da03092d47a3e1
Faulting application path: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
Faulting module path: C:\Program Files\Oracle\VirtualBox\Qt5GuiVBox.dll

[fth0]

Regarding the crash in the VirtualBox Manager (VirtualBox.exe), it happened while calculating the size of some GUI element to display it on a QScreen object that doesn't exist at that time. That's as close as I can get with my limited understanding of the Qt usage in VirtualBox.

Regarding the crash of the VM (VirtualBoxVM.exe), it happened in the Aud0Wr01 thread, which is part of the audio backend implementation. Removing audio from the VM and from the RDP connection could perhaps circumvent that crash.

Other than that, I can only suggest to create a ticket in the Bugtracker.

[PHolder]

I did open a ticket, it's here: https://www.virtualbox.org/ticket/21899

I just encountered a different entry in the Reliability Monitor, this is one where there was no dialog, I just came back to find the VM guest non-responsive and had to close it losing state.

Faulting application name: VirtualBox.exe, version: 7.0.12.9484, time stamp: 0x652832d4
Faulting module name: Qt5CoreVBox.dll, version: 5.15.2.0, time stamp: 0x606c96da
Exception code: 0xc0000005
Fault offset: 0x00000000001f1146
Faulting process id: 0x9a0
Faulting application start time: 0x01da0d34e763cf1f
Faulting application path: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
Faulting module path: C:\Program Files\Oracle\VirtualBox\Qt5CoreVBox.dll

[f1dad]

Hi, I get this exact same error once every day or two. I see there's no progress on the ticket you opened. Did you find any other solution to the problem?

[fth0]

FWIW, I've just commented on #21899.