From owner-freebsd-current Mon Jan 25 11:16:52 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA25782 for freebsd-current-outgoing; Mon, 25 Jan 1999 11:16:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from arg1.demon.co.uk (arg1.demon.co.uk [194.222.34.166]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA25776 for ; Mon, 25 Jan 1999 11:16:48 -0800 (PST) (envelope-from arg@arg1.demon.co.uk) Received: from localhost (arg@localhost) by arg1.demon.co.uk (8.8.8/8.8.8) with SMTP id SAA22387; Mon, 25 Jan 1999 18:28:11 GMT (envelope-from arg@arg1.demon.co.uk) Date: Mon, 25 Jan 1999 18:28:10 +0000 (GMT) From: Andrew Gordon X-Sender: arg@server.arg.sj.co.uk To: "Jordan K. Hubbard" cc: current@FreeBSD.ORG Subject: Re: 4.0-Current, netscape halts system In-Reply-To: <1476.917220230@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 24 Jan 1999, Jordan K. Hubbard wrote: > I really don't understand the problems that everyone is having, > myself. I've been running netscape (communicator 4.5) in -current for > ages now and just switched to 4.0 without any problems. My netscape > still continues to function just fine and has never crashed any of > my system so much as once. > > Why the wide disparity in experience, I wonder? One variable may be available memory. On my system, with default datasize limit of 16M from login.conf, Netscape coredumps very frequently. With datasize unlimited, Netscape eats all the available swap (this system is 64M real 128M swap) and kills the system that way. I currently run Netscape with datasize set to 64M, pending a new disc for more swap! In this configuration, Netscape either coredumps or starts behavhing oddly about once every 3 days, but at least I can just restart it rather than needing to reboot after a swap outage. Colour depth also has an effect - changing from 8-bit to 32-bit on the X server seems to have made this worse (as you might expect). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message