Date: Wed, 5 Nov 2008 18:28:21 +0100 From: Tijl Coosemans <tijl@ulyssis.org> To: Steve Polyack <korvus@comcast.net> Cc: freebsd-emulation@freebsd.org, questions@freebsd.org Subject: Re: flash9 checklist Message-ID: <200811051828.23041.tijl@ulyssis.org> In-Reply-To: <4911C914.1010705@comcast.net> References: <200810280859.24048@aldan> <200811051606.29361.tijl@ulyssis.org> <4911C914.1010705@comcast.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday 05 November 2008 17:25:56 Steve Polyack wrote: > Tijl Coosemans wrote: >> On Wednesday 05 November 2008 15:35:21 Steve Polyack wrote: >>> So I've done some more testing of this with various linux_base-* >>> installs. Youtube and most things (google maps) work with sound just >>> fine for a few seconds, but after trying to interact or letting them go >>> for a few minute they begin to rapidly eat up main memory. >>> npviewer.bin's usage will top out somewhere around 300-450MB before it >>> core dumps: pid 77684 (npviewer.bin), uid 1042: exited on signal 11 >>> (core dumped). This is on FreeBSD 7-STABLE i386 (as of Tue Oct 28) with >>> native Firefox 3.0.3 still. >> >> Do you have this with linux-firefox? > > Yes, I have the same behavior when using linux-firefox 2.0.17 from ports. Ok, so it's not a problem with npviewer.bin then. It's possible that when it's eating memory it's already coredumping. I've noticed that coredumps are generally a LOT bigger with 2.6.16 emulation compared to 2.4.2.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200811051828.23041.tijl>