Closed
Bug 306485
Opened 19 years ago
Closed 19 years ago
Firefox hangs in the morning....
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 299578
People
(Reporter: jbelanger, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6 I generally, start Firefox on Monday morning and would probably not shut it down until Friday, except for one ongoing problem, the browser hangs up first thing in the morning when I click on an email link to a web page, that should be displayed by Firefox. First let me tell you how I use Firefox during the day. Usually right after starting Firefox, I go to Webshots and look at a large number of gallery updates. I will create 5 tabs, one for a set of 30 updated galleries. I will then go to the last created tab and create 10 additional tabs, one for 10 of the 30 galleries. I will then go to the tab of the first updated gallery and create one tab for each picture that I wish to see more closely. A single gallery can have a number of gallery pages amnd will cause me to create 10 to 20 more tabs. After I have created all the picture tabs from a gallery, I will ctrl-w to close the gallery tab, and move on to the next gallery. I'll do this until the 10 galleries have been reviewed. I will then go through each of the picture tabs and if it contains a picture I wish to save, I will click on a link that will create a new Firefox windo (not a tab). I will use the right mouse button to save the picture to disk. I will then use ctrl-w to close this new window and the ctrl-w again to close the tab from which the window had been created. I will go through all the picture tabs, conditionally saving and closing all windows and tabs, until I'm back at the tab that contains the 30 updated galleries from which all this started. I'll take the next 10 galleries and do this all again. When I am done with the page of 30 update galleries, I'll close that with ctrl-w. I can potentially have approximately 100 tabs open at any one time. I notice that the memory utilization rises, and occassionally you can see the PC paging using a memory watcher. After doing all this, I'll visit a number of other web sites, not always the same from day to day and then go home for the evening, minimizing Firefox down to the tray (it will be on my companies internal home page, which does not have any dynamic features on it or automatic refreshing). In the morning, I'll be reading my email and one of the emails will have a link in it. When I click on the link, I can here the disk whirling away, apparently attempting to get Firefox paged back in or something. The CPU utilitization can go to 100% and stay that way for quite some time (I've seen 10 or more minutes pass by like this), but Firefox does not get raise up from the tray and the web page is nto displayed for this whole time. When I use the right mouse button to close Firefox, a dialog box is display indicating the Firefox is not responding and do I want to close it now. Which I do. I then start a fresh Firefox session, click on the web like from my email (Lotus Notes, if it matters), and the web page is immediately displayed. From what I can tell, it looks like Firefox is having some memory management problems. I don't know if it is related to tabbed browsing or not, but just the way the memory utilization numbers are looking and the way the system behaves in the morning, this seems like the most likely culprit. Reproducible: Sometimes Steps to Reproduce: 1.see above 2. 3. Actual Results: see above Expected Results: The software should behave identically from day to day, whether the browser was freshly started or been idle for many hours (assuming both are starting from the same place - my home page).
Comment 1•19 years ago
|
||
*** This bug has been marked as a duplicate of 299578 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•