Ticket #11998 (closed defect: obsolete)
VBox SVC - Potential memory leak
|Reported by:||CyberChris||Owned by:|
|Version:||VirtualBox 4.2.16||Keywords:||VBoxSVC Watcher memory cpu|
So I have been running several Windows XP guest machines now for a few weeks and noticed that the VBoxSVC process is constantly growing in resident memory usage.
I am using Ubuntu 13.04 with Virtual Box 4.2.10 (from the Ubuntu repo)
I have written a script that uses "vboxmanage" to start, get the info and stop 10 machines. This should hopefully simulate weeks of usage.
The key here is to not let the VBoxSVC process to exit, as this causes the problem to go away.
The real issue here is that the CPU usage goes right up to 100%. Crucially, the CPU usage of the "Watcher" thread over takes all the other threads.
I am not sure where the problem is after some initial debugging of the source code, however it feels like there is some sort of link list that is constantly growing which is then taking longer and longer to process. The issue here is it takes a long time to issue commands to the VM.
Shutting all of the VMs down so that the VBoxSVC process exits does resolve the issue, however is a major inconvenience.
If there is any further logs you require, please let me know. It may be worth mentioning that I have replicated this up from 4.2.10 - 4.2.16.