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

Abierto
  • ¿Algo no está bien?
#959 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 6 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
c
Área
desktop, networking

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.
Lenguaje dominante
C
Estrellas
1.4k
Forks
219
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de VirtualBox/virtualbox

Todos los issues de VirtualBox/virtualbox

Issues similares

Más issues de C

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.