[Bug]: VirtualBox Manager hangs and leaks memory when opening Port Forwarding settings on Windows 11
Maintainers usually reply within 6 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- c
- Domain
- desktop, networking
Research direction
Start by reviewing the attached VBoxSVC.log and Windows Error Reporting files alongside the VirtualBox Manager logs to identify where opening NAT Port Forwarding stalls. Then trace the relevant settings and port forwarding code paths; the issue does not name source files or tests. Done means the settings remain responsive and do not grow memory usage when all VMs are powered off.
Written by the indexing model from the issue text.
Description
VirtualBox_WER_AppHang_reports_20261106.zip
Users_huyvo_.VirtualBox_VBoxSVC.log
Version
7.2.22
Host OS Type
Windows
Host OS name + version
Windows 11, build 10.0.26200.9711
Host Architecture
x86
Guest OS Type
Linux
Guest Architecture
ARM
Guest OS name + version
No response
Component
Unspecified
What happened?
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.
- Dominant language
- C
- Stars
- 1.4k
- Forks
- 219
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from VirtualBox/virtualbox
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 84/100
VirtualBox/virtualbox#996 ·
Maintainers usually reply within 6 days
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
VirtualBox/virtualbox#979 ·
Maintainers usually reply within 6 days
-
[Bug]: Guest Additions 7.2.20 vboxvideo fails to build on Linux kernel 6.12.113 (drm_fb_helper_restore_fbdev_mode_unlocked: too few arguments)Possibly taken @Berbe claimed this 18 days ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
VirtualBox/virtualbox#918 · 9 comments ·
Maintainers usually reply within 6 days
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 25/100
VirtualBox/virtualbox#995 ·
Maintainers usually reply within 6 days
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 45/100
VirtualBox/virtualbox#994 ·
Maintainers usually reply within 6 days
All issues in VirtualBox/virtualbox
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
ESPresense/ESPresense#2680 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
ImageMagick/ImageMagick#9134 ·
Maintainers usually reply within 1 day
-
Builder: a structure opened without calculation data shows the Diffraction (fibre) view by defaultOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
FriendsofECCE/ECCE#1245 · 1 comment ·
-
Arch: ARM/AArch64 Doc
Difficulty 1/5 Under an hour Newbie friendliness 90/100
RT-Thread/rt-thread#12082 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
apache/nuttx-apps#4108 · 4 comments ·
Maintainers usually reply within 1 day