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 <http://home.wxs.nl/~asmodai> BSD & picoBSD: The Power to Serve <http://www.freebsd.org> To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message