Closed
Bug 299349
Opened 20 years ago
Closed 19 years ago
Browser uses up alot of memory (latest 1.7)
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: wellander2, Unassigned)
Details
Hi, When using the latest 1.7 nightly build from the 1.7 branch for windows the browser uses up alot of memory that eventually crashes it. Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.9) Gecko/20050630 is the build. How to reproduce: 1. download that build from the nightly directory 2. browser with it for a minute or two 3. see it use alot of memory What the browser should of done: Not use alot of memory. It happens all of the time when I use it. This is a regression? I am using windows 2000.
http://www.savefile.com/filehost/files3.php?fid=5681266 This my memory usage file.
Hi, The problems are worse in Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.9) Gecko/20050701 This is a serious problem.
Hi, Fixed in Mozilla Mozilla 1.7.9 Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.9) Gecko/20050702
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Comment 4•19 years ago
|
||
No specific bug / patch referenced as the fix. -> WORKSFORME
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
Updated•19 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago → 19 years ago
Resolution: --- → WORKSFORME
(In reply to comment #3) > Hi, > Fixed in Mozilla > Mozilla 1.7.9 > Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.9) Gecko/20050702 I still have the same problem with mozilla 1.7.12
Hi, I am reopening this per requests. I will let other people decide on what to do with this bug.
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Comment 8•19 years ago
|
||
This is a vague bug about an old version. Invalid. Please don't reopen this bug; file new bugs if you have information about actual leaks or memory issues (preferrably in a newer version).
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago → 19 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•