[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sparc-redhat
Subject:    S/Linux, Netscape and memory leaks?
From:       SpaceDust <spcdust () li ! net>
Date:       1998-05-18 23:07:29
[Download RAW message or body]

The last couple of days my LX has totally locked up after using Netscape
a few times.  Since I've been running 2.1.89 since Jim Moody offered it
up, without any problems (except for not being able to boot with the
CD-ROM hooked up), I am somewhat hesitant about blaming the kernel.

Yesterday after rebooting Top had me running 7 Mb out of 96 when in CLI. 
After starting X, I was using 17 Mb.  Now I start up Netscape, and it
pumps up to 28 Mb.  Okay fine.  After I close netscape, the memory is
not
clearing out.  When I start up Netscape again, now top shows 39 Mb of
memory being used.  It continues on this way, until you can't start
Netscape (not enough memory available)  

I'm not Linux expert, (as a matter of fact many of you have probably
forgotten more than I know) but isn't Netscape supposed to clear out of
memory after it closes?  If so, shouldn't top then show a drop in memory
usage?  

Is there a way for me to reclaim this memory without having to reboot?
Is this a Netscape thing, or a S/Linux thing?

If it matters, I have an LX with 96 Mb of Ram and a 50 Mb swap.

SpaceDust
-- 
.___________________________________________________________________.
:                                                                   :
:   While you're spamming me, don't forget to include these guys:   :
:   rhundt@fcc.gov jquello@fcc.gov sness@fcc.gov rchong@fcc.gov     : 
: customer@email.usps.gov fraudinfo@psinet.com consumerline@ftc.gov :
:        admin@loopback $LOGIN@localhost  $LOGNAME@localhost        : 
:  $USER@localhost: $USER@$HOST -h1024@localhost root@mailloop.com  :
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

-- 
To unsubscribe: mail -s unsubscribe sparc-list-request@redhat.com < /dev/null

[prev in list] [next in list] [prev in thread] [next in thread]