VirtualBox

Opened 12 years ago

Closed 12 years ago

Last modified 11 years ago

#10808 closed defect (fixed)

Large mem leak in vboxtray.exe => Fixed in SVN

Reported by: Brussel Owned by:
Component: guest additions Version: VirtualBox 4.1.18
Keywords: vboxtray leak Cc:
Guest type: Windows Host type: Windows

Description

On my WinXP guest, the vboxtray.exe gobbles memory at approx 800 KB pr hour. Initial allocation is 2.4 MB and after a day its ~20 MB.

Host: Win2008R2 Guest: Win XP, sp3, 32 bit

I have a attached both the 4.1.18 log as well as the 4.1.16, which displayed similar behaviour.

The winxp guest is lean and mean and all unnessesary service and processes are stopped - this includes normally running services, such as the eventlog. I'm guessing it might be a handle leak when trying to open stopped services.

Attachments (2)

vbox.log (37.3 KB ) - added by Brussel 12 years ago.
4.1.18 log
vbox16.log (72.2 KB ) - added by Brussel 12 years ago.
4.1.16 log

Download all attachments as: .zip

Change History (6)

by Brussel, 12 years ago

Attachment: vbox.log added

4.1.18 log

by Brussel, 12 years ago

Attachment: vbox16.log added

4.1.16 log

comment:1 by Brussel, 12 years ago

Forgot to mention that the guest os just logs in and then idles the whole time. No application is activly running nor screensaver or power save is active.

comment:2 by Frank Mehnert, 12 years ago

Summary: Large mem leak in vboxtray.exeLarge mem leak in vboxtray.exe => Fixed in SVN

Thanks for the report! Reproduced and fixed.

comment:3 by Frank Mehnert, 12 years ago

Resolution: fixed
Status: newclosed

Fixed in 4.1.22.

comment:4 by Devbox, 11 years ago

WinXP: vboxtray.exe stops functioning sometimes at around 512kb, which instead of a full restart used to close the vboxtray.exe and relaunch to have it work again however it since one of the early 4.2.0 updates even after relaunching memory of the vboxtray.exe memory goes up to around 2-3MB and only works for a single clipboard act becoming inoperable until machine is restarted.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use