Date: Tue, 01 Jun 2010 14:54:52 +0900 From: Daichi GOTO <daichi@freebsd.org> To: freebsd-emulation@freebsd.org Subject: Re: CFT: VirtualBox 3.2.0 Message-ID: <4C04A0AC.50700@freebsd.org> In-Reply-To: <5bae657843a7c00f05c14c2bed884364@bluelife.at> References: <4C011524.7050806@FreeBSD.org> "<4C0259D8.2000902@freebsd.org>" <4C031860.6070802@freebsd.org> <20100531085555.GB55614@heechee.tobez.org> <4C03B42B.2080206@protected-networks.net> <5bae657843a7c00f05c14c2bed884364@bluelife.at>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2010/06/01 00:14, Bernhard Froehlich wrote:
> On Mon, 31 May 2010 09:05:47 -0400, Michael Butler
> <imb@protected-networks.net> wrote:
>> On 05/31/10 04:55, Anton Berezin wrote:
>>> On Mon, May 31, 2010 at 11:01:04AM +0900, Daichi GOTO wrote:
>>>> Memory leaks there I have noticed. Look at follow message of top(1):
>>>
>>> I also experience memory leaks. WinXP guest, amd64-CURRENT (from
>>> 2010-05-10) host. 100% CPU load when the guest is doing nothing, and
>>> memory
>>> usage keeps growing at a rather alarming pace.
>>
>> Just an observation - this appears to be related to using the additions
>> from 3.2.0. Using VBox 3.2.0 with the 3.1.8 additions doesn't appear to
>> display the leak - no idea what triggers this behaviour,
>
> I've just talked to the virtualbox developers and this is obviously an
> known bug in the 3.2.0 additions. As a workaround you can use the 3.1.8
> additions and they said it will be fixed with 3.2.2.
Workaround looks working well:
GuestOS:
WinXP, Win7 with guest addition 3.1.8
Host:
VirtualBox 3.2.0 / FreeBSD 9-current
> Thanks!
--
Daichi GOTO
81-42-316-7945 | daichi@ongs.co.jp | http://www.ongs.co.jp
LinkedIn: http://linkedin.com/in/daichigoto
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C04A0AC.50700>