Bug 11243 - redhat6.2 becomes very slow after browsing with netscape
redhat6.2 becomes very slow after browsing with netscape
Product: Red Hat Linux
Classification: Retired
Component: netscape (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Depends On:
  Show dependency treegraph
Reported: 2000-05-05 10:45 EDT by K. Hellenthal
Modified: 2014-03-16 22:13 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-07-13 10:41:39 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description K. Hellenthal 2000-05-05 10:45:09 EDT
I upgraded my system from 6.0 to 6.2. This went very smoothly.All my old
settings where still there. When starting to browse with netscape the
system starts accessing the Hard disk constantly after having accessed
about 4 web sites. The mouse is also not responding very well anymore. If I
manage to kill netscape via kill -9 <process> everything gets back to
normal again.
Comment 1 cmilton 2000-05-28 19:32:59 EDT
I find that if I leave Netscape 4.7.2, and now that I've upgraded to 4.7.3, too,
that if I leave Netscape on for more than 4 hours, connected to the net or not,
Netscape takes all available memory and then some, cause everything to slow
down, and reaction to input gets out of sync. If I have more than 4 Netscape
windows open, the leak gets bad quickly. Once I managed to get top running
and saw that Netscape had an RSS of 150M and high priority.
Comment 2 tannhaus 2000-06-02 01:12:25 EDT
I can vouch for this.  I have 256 megs of ram and I begin swapping when running
netscape.  It appears to have a huge memory leak.
Comment 3 Sean Murphy 2000-07-13 10:41:39 EDT
Exact same problem here.  I have 128 MB of RAM and after a little bit of Netscape usage, my memory usage pegs and never goes back down until I 
top, find the id # for netscape, and kill it with a signal 9.  I think I've noticed that it does it after I access a web page with either java/javascript, but I 
haven't tested this theory enough to verify it.

Pertinent info:
350 MHz Pentium II
Running helix_gnome 1.2 with latest version of Sawfish
Comment 4 Bill Nottingham 2000-07-18 12:24:26 EDT
Unfortunately, we can't really fix bugs like this inside netscape.

You're best off reporting this to Netscape directly via:


Note You need to log in before you can comment on or make changes to this bug.