You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: VirtualBox Manager hangs and leaks memory when opening Port Forwarding settings on Windows 11 #959
VirtualBox Manager becomes unresponsive when opening a VM's Settings dialog, especially when accessing Network > NAT > Port Forwarding.
The issue also occurs when all virtual machines are powered off. At the time of the failure, VBoxManage list runningvms returns no running VMs, but VirtualBox.exe stops responding while VBoxSVC.exe remains running.
Windows reports an AppHangXProcB1 event involving VirtualBox.exe and VBoxSVC.exe. The VirtualBox Manager process grows significantly in memory usage before becoming unresponsive.
Expected behavior:
The Settings dialog should open normally and allow the VM configuration and port forwarding rules to be viewed or edited, regardless of whether the VM is running.
Environment:
VirtualBox 7.2.22 r175245
Windows 11, build 10.0.26200.9711
Lenovo ThinkPad P15 Gen 2i
No VirtualBox Extension Pack installed
Affected VMs use NAT networking
The complete VBoxSVC.log, selectorwindow.log, VirtualBox Manager logs, and Windows Error Reporting files are attached.
How can we reproduce this?
Install VirtualBox 7.2.22 r175245 on Windows 11.
Create or import one or more virtual machines using NAT networking.
Power off all virtual machines.
Start VirtualBox Manager.
Right-click a VM and select Settings.
Open the Network section.
Select NAT and open Port Forwarding.
Wait until the Settings dialog or VirtualBox Manager becomes unresponsive.
Check the process state in Windows Task Manager.
Run VBoxManage list runningvms and verify that no VMs are running.
Observed result:
VirtualBox Manager may stop responding while VBoxSVC.exe remains running. Windows may record an AppHangXProcB1 event identifying VBoxSVC.exe in the hang report.
Expected result:
The Settings and Port Forwarding dialogs should open and remain responsive when all VMs are powered off.
The attached logs were collected immediately after reproducing the issue.
Did you upload all of your necessary log files, screenshots, etc.?
Yes, I've uploaded all pertinent files to this issue.
Activity