Opened 12 years ago
Closed 12 years ago
#10801 closed defect (fixed)
~25 MB memory leak when changing nic1 from null to nat => Fixed in SVN
Reported by: | tehnicaorg | Owned by: | |
---|---|---|---|
Component: | network/NAT | Version: | VirtualBox 4.1.18 |
Keywords: | Cc: | ||
Guest type: | other | Host type: | Windows |
Description
Hello,
Running this .bat
:a "C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" controlvm "xp" nic1 null sleep 5s "C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" controlvm "xp" nic1 nat sleep 5s goto a
would increase the private memory of VirtualBox.exe (as seen by Process Explorer) by about 25 MB every time nic1 is switched from null to nat. (a lot faster if you remove the sleeps) VirtualBox.exe starts with about 70-80 MB private memory and will grow fast after running the batch.
I've reproduced this with two VMs, one with Ubuntu 64, running or in VirtualBox's BIOS also, and one without a hard drive attached (XP, 32 bit), direcly in BIOS (I've pressed F12 when booting).
My initial problem was a crash in VBoxDD.dll which I've tried to reproduce (then I've only switched the nic a couple of times, to 'bridged' too).
Host: Windows 7 x64, SP1.
Attachments (1)
Change History (4)
by , 12 years ago
comment:1 by , 12 years ago
Thanks for the report! That leak will be fixed in the upcoming 4.2 release.
comment:2 by , 12 years ago
Summary: | ~25 MB memory leak when changing nic1 from null to nat → ~25 MB memory leak when changing nic1 from null to nat => Fixed in SVN |
---|
comment:3 by , 12 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Fix is part of VBox 4.2.0. Future maintenance releases of VBox 4.1.x will have that fix as well.
Vbox.log and vm info logs.