Ticket #11309 (new defect)

Opened 16 months ago

Last modified 3 days ago

VirtualBox lingers in memory as the existing VBoxSVC process just exited

Reported by: mhanor Owned by:
Priority: minor Component: other
Version: VirtualBox 4.2.6 Keywords:
Cc: Guest type: all
Host type: Windows


This is not particular to 4.2.6. Host: Windows 7 SP1 x64

Starting VirtualBox.exe as the existing VBoxSVC process is just exiting (normal termination a few seconds after the previous VirtualBox instance exited), the new VirtualBox process does nothing. It just lingers in memory. The issue can be reproduced if you correctly time your launch of the VirtualBox program, paying attention to the existing VBoxSVC process, taking into account how long ago the previous VirtualBox instance exited.

Change History

comment:1 Changed 13 months ago by mhanor

VB 4.2.8 has the same problem.

comment:2 Changed 3 days ago by mhanor

It's the same problem with VB 4.3.11 rev93259. The VirtualBox process actually returns an error, after some time:

Callee RC: 

To rephrase the issue: when launching VirtualBox, just when the VirtualBox COM service (VBoxSVC) is about to close (normal termination, after the previous, last instance of VirtualBox, was closed), the new VirtualBox process fails to syncronize with the existing (about to be closed) VBoxSVC process. In the end, it fails with the above error.

Last edited 3 days ago by mhanor (previous) (diff)
Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use