Date: Wed, 5 Jun 1996 15:40:38 -0700 (PDT) From: Jake Hamby <jehamby@lightside.com> To: Gary Jennejohn <Gary.Jennejohn@munich.netsurf.de> Cc: freebsd-current@FreeBSD.org Subject: Re: More on VM, swap leaks Message-ID: <Pine.AUX.3.91.960605153746.25391B-100000@covina.lightside.com> In-Reply-To: <199606052334.XAA13656@peedub.gj.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 5 Jun 1996, Gary Jennejohn wrote: > I decided to test this out. I can start both emacs and xemacs with NO > failures at all. And not one additional block of swap gets allocated. > I must in all fairness note that I already had about 16 MB of swap in > use. > > This with a -current kernel made from the latest sources as of Monday. > So I didn't test against the latest pmap.c, et. al. But I wouldn't > expect this to have a negative effect. > > This is on a machine with 16 MB memory and 64 MB swap. > > Looks to me like you might have a bad SIMM, Greg. Another possibility is a bad emacs binary. Especially since as part of the compilation process, emacs runs itself, loads in a bunch of LISP, then pukes itself out as a new executable. I shudder to think what could happen if a buggy kernel or bad SIMM decided to rear its head at that point. By the way, I'll be building emacs 19.31, among other things, this week, with FreeBSD-current and Solaris/x86, so I'll post if I have any problems with the new pmap code. Also, I'm using GCC 2.7.2 with 2.7.3 patches and -O2, to try to shake out any optimizer bugs before 2.7.3 is officially released (and if I find none, to encourage us to put 2.7.3 in -current!). ---Jake
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.AUX.3.91.960605153746.25391B-100000>