On Nov 12, Michael O'Donnell claimed:
> Memory exhaustion seems to be a popular theory for Netscape's
> crappy behavior but now I'm running it on a system w/256Mb
> RAM (where everything else seems rock-solid) and it's just
> as unreliable as ever.
Even on a 256MB system, this is still likely a big reason why it craps out
on you. I have a similar setup at work (256MB, no Java, yes to
Javascript) and also a memory monitor. I don't run that much memory
intensive stuff, but I still see my memory usage going up the longer a
session of NS is running. Once it hits the swap space, I usually will
killa netscape and restart it ... that (more often than not) resets my
memory usage back to about 80MB or so.
-Cole
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
