Opened 3 months ago

Closed 3 months ago

#21999 closed defect (wontfix)

VBoxIntNetSwitch process requires force quit

Reported by: aaaaa2 Owned by:
Component: network Version: VirtualBox-7.0.14
Keywords: VBoxIntNetSwitch Whonix Cc:
Guest type: Linux Host type: Mac OS X


This is a continuation from ticket #21752 (see it for more details). The VBoxIntNetSwitch process doesn't seem to leak memory anymore but doesn't quit on its own when VirtualBox is quit. One has to go to Activity Monitor and Force Quit the process.

Reproduction Steps:

  1. Use two VMs that communicate with each other over the internal network.
  1. Shut down both VMs and VirtualBox itself.
  1. Observe if the VBoxIntNetSwitch process is open in macOS’ Activity Monitor.
  1. Try to Quit the process. If it won’t close, Force Quit the process.

Expected Behavior:

Closing the VMs stops the VBoxIntNetSwitch process.

Actual Behavior:

Closing the VMs does not stop the VBoxIntNetSwitch process, causing it to stay alive. The process has to be Force Quit.

Software Versions and Processor Type:

macOS Monterey 12.7.3

Intel x86 processor

VirtualBox 7.0.14

Change History (2)

comment:1 by aeichner, 3 months ago

This is actually expected, the VBoxIntNetSwitch process runs as an XPC service (because it internally uses the XPC API for the interprocess communication between all the different possible participants in an internal network). macOS manages the lifetime of the service over which we have no influence (except maybe crashing it deliberately when the network goes down but that will cause annoying pop-ups ;) or XPC will just restart the service ). macOS keeps XPC services idling unless there is some resource shortage causing it to recycle those services.

comment:2 by aeichner, 3 months ago

Resolution: wontfix
Status: newclosed
Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use