Saturday, April 4, 2015

windows - What could be causing such a high commit charge in XP?


I was getting out of memory errors running virtual machines in VirtualBox so I checked my commit charge and lo and behold, it's 1913 MB!


I only have 2GB physical RAM.


After closing all "applications" I have 1800 or so MB still in commit charge. That's the majority of my RAM. Opening process explorer shows no processes that seem out of order, the biggest memory hog being process explorer itself at about 26MB and everything else quite a bit smaller.


Can windows "leak" memory? Should I suspect a driver or something like the Symantec antivirus? Would their memory use even show up in process explorer somehow?


After further investigation I believe this is a VirtualBox related issue. For some reason after terminating some virtual machines, even after terminating VirtualBox, it was not freeing the memory allocated to them. For another reason I can't figure out, the task manager / process explorer cannot see the memory allocated to virtual machines in VirtualBox. It is does not show up on any process or task list. The only sign that it is happening is that the commit charge rises.


Answer



Seems it is an issue with VirtualBox.


I have turned off Intel Virtualization Technology in Virtualbox as suggested in another forum and haven't had problems so far.


No comments:

Post a Comment

linux - How to SSH to ec2 instance in VPC private subnet via NAT server

I have created a VPC in aws with a public subnet and a private subnet. The private subnet does not have direct access to external network. S...