296603 - browser gets progressively slower, no matter what pages/no of pages to the point of not responding. response time improves after restarting

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[Court]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4

After browsing for some time >30mins the browser networking becomes increasingly
slower to the point of stopping without any response from the browser. Happens
with any type of page. It is the length of time a single copy of Firefox is open
ie greater than 30 mins that the network communication slow to a halt.
Restarting the browser seems to improve the situation but it again progressively
slows to a halt after some time.

Reproducible: Always

Steps to Reproduce:
1. Start browser
2. Browse for greater than 30 -45 minutes
3.

Actual Results:  
The browser networking functions halted making the browser unusable. any pages
attempted to be loaded after this do not get loaded. stopping a page half way
through loading seems to expediate the problem

Expected Results:  
Should proceed to load pages at the same pace as when first started

Comment 1

[Chris Blore]

Have you tried a complete removal and reinstall of Firefox? Do you have any
extensions or themes installed that could be causing this problem?

Comment 2

[Court]

(In reply to comment #1)
> Have you tried a complete removal and reinstall of Firefox? Do you have any
> extensions or themes installed that could be causing this problem?

Yes, i have done reinstalls a couple of times, no themes or extensions apart
from the defaults...

Comment 3

[djpohly]

Reporter,

Can you reproduce this using a nightly build of Firefox?  There have been many
fixes for these builds since May 2004 that are not part of the 1.0.x releases. 
Get a nightly here and try it out:
http://www.mozilla.org/developer/#builds

Comment 4

[Court]

(In reply to comment #3)
> Reporter,
> 
> Can you reproduce this using a nightly build of Firefox?  There have been many
> fixes for these builds since May 2004 that are not part of the 1.0.x releases. 
> Get a nightly here and try it out:
> http://www.mozilla.org/developer/#builds

I have recently installed deer park alpha, will see if the same occurs - my
thoughts that it may be a network driver problem have been somewhat tested by
opening other browser variants available "at the same time" as I experience the
problem in firefox.

If I experience any other problems or if the problem goes away with this build
then I will post accordingly...

Comment 5

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 6

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.