[Bug]: VirtualBox Manager hangs and leaks memory when opening Port Forwarding settings on Windows 11

Ouverte
  • Quelque chose ne va pas ?
#959 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 6 jours

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
25/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
c
Domaine
desktop, networking

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

bug

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?
  1. Install VirtualBox 7.2.22 r175245 on Windows 11.
  2. Create or import one or more virtual machines using NAT networking.
  3. Power off all virtual machines.
  4. Start VirtualBox Manager.
  5. Right-click a VM and select Settings.
  6. Open the Network section.
  7. Select NAT and open Port Forwarding.
  8. Wait until the Settings dialog or VirtualBox Manager becomes unresponsive.
  9. Check the process state in Windows Task Manager.
  10. 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.
Langage dominant
C
Étoiles
1.4k
Forks
219
Aucune PR mergée en 30 j

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de VirtualBox/virtualbox

Toutes les issues de VirtualBox/virtualbox

Issues similaires

Plus d'issues C

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.