From owner-freebsd-current Mon Jan 25 22:37:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA13149 for freebsd-current-outgoing; Mon, 25 Jan 1999 22:37:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.wxs.nl (smtp02.wxs.nl [195.121.6.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA13138 for ; Mon, 25 Jan 1999 22:37:54 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.57.77]) by smtp02.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAAAA8; Tue, 26 Jan 1999 07:37:53 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 26 Jan 1999 07:46:18 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Andrew Gordon Subject: Re: 4.0-Current, netscape halts system Cc: current@FreeBSD.ORG, Matthew Dillon Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 26-Jan-99 Andrew Gordon wrote: > On Mon, 25 Jan 1999, Matthew Dillon wrote: >> :One variable may be available memory. On my system, with default >> :datasize >> :limit of 16M from login.conf, Netscape coredumps very frequently. With >> >> I've been using netscape on a 24bit color system for well over a >> year and have never had a serious memory leak problem or X >> session ( or machine ) crashing due to it. I don't leave the >> netscape window open all the time, though... I tend to exit >> out of it when I'm not using it. This would indicate that it might have to do then with prolonged exposure to memory and the memory-system(s) (swap, paging). Is there anyway to monitor the syscalls and the amount of memory used and released by each call Matt? Hope ye see where I'm getting at... > 1) I'm not sure I would necesarily accuse Netscape of having a leak: > what with caching pages in RAM and the allocation policy of whatever > malloc they use, maybe it really needs this much and would stabilise > at some size of 100M+ - I just don't have the swap space to find out. Yer kidding right? A program that _needs_ 100 MB or more? Surely yer kidding... I haven't seen a program in normal corporate/home use that justifies the memory usage of 100 MB or more including NetScape's Navigator/Communicator. > 2) I have never seen a system crash as such. However, having the X > server killed due to out-of-swap leaves the console fouled up and so > could easily be mis-described as a crash. I wonder if X could be the originator of the problems, my guess is it can't since Linux uses the same X and I haven't heard any complaints from that corner. Also it's nice that the program dumps core, but afaik without debug symbols it's not much use. --- Jeroen Ruigrok van der Werven It's a Dance of Energy, asmodai(at)wxs.nl when the Mind goes Binary... Network/Security Specialist BSD & picoBSD: The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message