VirtualBox

Ticket #6838 (closed defect: fixed)

Opened 4 years ago

Last modified 4 years ago

Memory Leak Windows 7

Reported by: miracle15 Owned by:
Priority: major Component: other
Version: VirtualBox 3.2.0 Keywords: Windows 7
Cc: Guest type: Windows
Host type: Windows

Description

Hi, I'm Running a Windows 7 32Bit Professional Edition as a Guest System in Virtual Box. The Host System is a Windows 7 64Bit Professional Edition. After using the Virtual Box for roughly 4 days the VirtualBox blocks 40% of the hosts RAM. Even after shutting down the guest an Virtual Box the RAM still isn't released and i have to restart the whole Host-system to clean the RAM from the VirtualBox Fragments.

Attachments

VBox-beginning.log Download (66.8 KB) - added by miracle15 4 years ago.
Log from the original run which allocates 40% of the Hosts RAM until 90% Host RAM is full
VBox-restart.log Download (65.1 KB) - added by miracle15 4 years ago.
Restart of Guest System roughly 1 hour after shutdown

Change History

Changed 4 years ago by miracle15

Log from the original run which allocates 40% of the Hosts RAM until 90% Host RAM is full

Changed 4 years ago by miracle15

Restart of Guest System roughly 1 hour after shutdown

comment:1 Changed 4 years ago by LRN

I'm running VBox 3.2.0 r61806 on Windows 7 x64 Ultimate N host, with Debian as a guest OS.

I've noticed that i'm running out of physical memory pretty fast, and that all killing applications and daemons in Windows doesn't free much memory (about 4GB out of 8GB is still held by something), and remaining processes are lightweight enough.

Memory clears after reboot.

I ran poolmon -u -n e:\poolmon01.txt (poolmon from WDK) and it reported this:

Tag Type Allocs Frees Diff Bytes Per Alloc

VBNF Nonp 56777859 2433 56775426 5573217088 98

which means that the driver tagged as VBNF (which corresponds to VBoxNetFlt.sys) consumed 5 573 217 088 bytes of non-paged memory by making 56777859 allocs with only 2433 frees

comment:2 Changed 4 years ago by LRN

It goes without saying that i've downgraded to 3.1.8 immediately after submitting the comment above.

comment:3 Changed 4 years ago by frank

  • Status changed from new to closed
  • Resolution set to fixed

Please reopen if this problem is still relevant with VBox 3.2.6.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use