vboxsvc mem leak 2.02 puel vista host?

Post by **sandervl** » 16. Sep 2008, 20:40

I've tried both the x86 and x64 hotfixes and they unzip just fine. You'll find an msu file that you can run to install the hotfix.

plong · Post by **plong** » 16. Sep 2008, 22:32

I can't install the hotfix. Any suggestions as to what I do now besides wait for the next software update from Microsoft which includes this fix?

I wrote:...when prompted for the password contained in the email, I duly entered it. I then got the "error code is 40" error when the installer was trying to unzip the hotfix.

Thinking that maybe the file I downloaded was corrupt (I know this is a reach), I requested and received another copy at a different email address. I get the same error message, though. Surprise. I'm cursed.

I wrote:However, when the installer prompts for the password, there is a "Skip" button, as if the password is optional. I clicked it, and then got this message:

"All files were successfully unzipped."

Apparently, this is a bug in the Microsoft hotfix installer. The above message is incorrect--in fact, <i>no</i> files were successfully unzipped.

I wrote:It seems that the CPU load is now much lower when running VirtualBox 2.0.2, but after using it a while, the load does go up noticeably.

But I was mistaken. I'm still experiencing the same CPU/memory load issue. <sigh...>

plong · Post by **plong** » 17. Sep 2008, 00:12

I wrote:I can't install the hotfix. ... I'm still experiencing the same CPU/memory load issue. <sigh...>

It was a Vista file-permission thing. The default location in the installer was C:\. I didn't care, so I accepted it. From a thread in a Microsoft discussion group, I learned that there might be an issue with where one is trying to unzip to. Sure enough, I specified another folder, and it unzipped.

I ran the installer, rebooted, and now VirtualBox 2.0.2 is running very smoothly!

skrowl · Post by **skrowl** » 17. Sep 2008, 04:03

Perhaps the installer should check for the presence of this hotfix before installing versions of VirtualBox that require it to work properly?

strips · Post by **strips** » 18. Sep 2008, 20:30

My! I really loathe Microsoft!

I could not find any support channel / email that was free of charge. I have to pay 500NOK or abour 85 USD for each call or e-mail.

Where did you guys contact them?

Of course I would never pay money for something that should be free I found this site with the hotfix:
http://itsvista.com/2008/04/kb949700/

UPDATE:

It worked like a charm. Have been using my VM extensivly for a couple of hours and still going strong.

Regards
stian

Post by **sandervl** » 19. Sep 2008, 09:06

We have rewritten the code that uses the Windows API addressed by the hotfix. Its usage was responsible for more than just memory leaks.

See this ticket.

ejan · Post by **ejan** » 24. Sep 2008, 15:04

I installed the hotfix and the issue seems to have fixed. I've been running my guest OS for over three hours now and the VBoxSVC.exe is using just a little over 13MB of memory. It started at 3MB, though, and I'm wondering if the issue has fixed or the hotfix just made the memory leak super slow.

My environment:
-------------------
Host OS: Windows Vista Business 32 Bit
Machine: Lenovo ThinkPad T61
Host RAM: 3GB
Guest OS: Windows XP Professional SP2
Guest RAM: 1GB

Elektroschnitzel · Post by **Elektroschnitzel** » 8. Oct 2008, 14:46

I also installed the Hotfix and it seens to be fixed.

Vista Business
Dell Vostro 1700
2GB RAM
350 MB dedicated to Virtual XP SP3
8MB Graphik Memory

tiresias1 · Post by **tiresias1** » 11. Oct 2008, 17:58

I had the same problem on Vista and it looks like the Microsoft update is NOT needed.

Instead I just installed the VirtualBox patch linked by sandervl above

http://www.virtualbox.org/ticket/2212#comment:35

It is a zip file containing two files which you replace in the VirtalBox version 2.0.2 installation folder (you need Admin status to do this). Remember to keep a copy of the existing files.

The restart VirtualBox. Help->About will now say version 2.0.2_AQ

I was amazed that after a couple of hours the VBoxSVC.exe was still using 0% CPU - in fact I've never seen it use any CPU time at all!

Prior to that I think it was continuously using 10% from startup, increasing to 50% or more.

I'd advise anyone experiencing this problem to install the VirtualBox patch instead of the suggested Microsoft update.

Also the VirtualBox home page which mentions installing the Microsoft update could possibly do with being changed.

virtualbox.org

vboxsvc mem leak 2.02 puel vista host?

Re: Hotfix password not needed?

Hotfix self-extractor couldn't extract to C:\ on Vista

2.0.3 idea