Closed
Bug 196055
Opened 22 years ago
Closed 22 years ago
mozilla performance degrades over time while browser is open
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
People
(Reporter: jade01313, Assigned: asa)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030207
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030207
my morning routine is to hit /., g00glenews, and a few other pages (luv tabbed
homepages) to see what stories are out there that i'm interested in reading. i
generally open up a number of stories in multiple tabs, and then minimize the
browser and read the stories over time through my day.
since upgrading to a nightly build of 1.3 (wanted to try spam filters) i have
noticed that the longer mozilla is open, the slower it responds over time. for
instance, when i initially open the browser (reguardless of # of tabs)
performance is quite good and snappy for minimize/restore, changing between
tabs, etc.
as the day progresses however, the browser becomes sluggish quite quickly. if
my browser is open for more than 3-4 hours, a restore from a minimize can take
over 10-15 seconds to complete.
also, when the browser has been open for a couple of hours, and then i close it,
i have noticed a very large increase in the amount of time it takes mozilla to
clear out the quick load icon from the sys-tray. if i open mozilla and then
close it relatively quickly (less than an hour) the reload of the systray icon
is quite fast, but after a longer day w/ the browser open, the time it takes for
the icon to disapear (unload?) and then reappear (reload?) becomes significantly
longer, approaching 30 seconds at times.
this sluggishness seems to *only* come about when the actually browser is open,
*not* when the browser is closed and the quickload has been in the systray for
an extended period.
i have not sat down w/ a stopwatch to see if the number of tabs open influences
this degredation...
Reproducible: Always
Steps to Reproduce:
1. open mozilla and open between 4-20 diff pages in diff tabs
2. minimize and restore
3. note quick response and redraw of window
4. minimize
5. wait 1 hour
6. restore; note slightly slower response time for redraw of window
7. minimize
8. wait 3 hours
9. restore; note significantly slower response time
Actual Results:
performance degraded
Expected Results:
performance should not be dependent on the amt of time the browser is open...
it seems like there's a mem leak somewhere or something... which doesn't make
much sense...
perhaps calling the garbage collector and forcing it to clean out the garbage
every 5-10 min or so that the browser is open would solve the problem...
Comment 1•22 years ago
|
||
*** This bug has been marked as a duplicate of 76831 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 2•22 years ago
|
||
doh... sry for the dupe... i searched... :(
m/b one of those g00gle appliance boxes would make searching easier ;) or, i
guess, i could spend more time searching... that would be cheaper...
btw: Debug->Leak Detector->Dump Memory Leaks seems to restore normal
functionality...
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•