Date: Mon, 31 May 2010 19:42:57 -0500 From: Brandon Gooch <jamesbrandongooch@gmail.com> To: Mario Lobo <lobo@bsd.com.br> Cc: freebsd-emulation@freebsd.org Subject: Re: CFT: VirtualBox 3.2.0 Message-ID: <AANLkTimHYbFXai9_kuGQLij7a9VseAQTByk2W3wY_Szc@mail.gmail.com> In-Reply-To: <201005311906.30257.lobo@bsd.com.br> References: <4C011524.7050806@FreeBSD.org> <4C03B42B.2080206@protected-networks.net> <5bae657843a7c00f05c14c2bed884364@bluelife.at> <201005311906.30257.lobo@bsd.com.br>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, May 31, 2010 at 2:06 PM, Mario Lobo <lobo@bsd.com.br> wrote: > On Monday 31 May 2010 15:14:01 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. =A0WinXP guest, amd64-CURRENT (from >> >> 2010-05-10) host. =A0100% CPU load when the guest is doing nothing, a= nd >> >> memory >> >> usage keeps growing at a rather alarming pace. >> > >> > Just an observation - this appears to be related to using the addition= s >> > from 3.2.0. Using VBox 3.2.0 with the 3.1.8 additions doesn't appear t= o >> > 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. >> >> Thanks! >> > > Actually, this problem doesn't happen up to > VBoxGuestAdditions_3.2.0_BETA1.iso. > > VBoxGuestAdditions_3.2.0_BETA2.iso and newer do have it. I can confirm this. For the record. -Brandon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTimHYbFXai9_kuGQLij7a9VseAQTByk2W3wY_Szc>