Ticket #11309 (new defect)
VirtualBox lingers in memory as the existing VBoxSVC process just exited
|Reported by:||mhanor||Owned by:|
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.