Closed Bug 466381 Opened 16 years ago Closed 15 years ago

After history search and closed history window, browsing presents little freezes and high cpu usage

Categories

(Firefox :: Bookmarks & History, defect)

3.0 Branch
x86
macOS
defect
Not set
minor

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: lfbitt, Unassigned)

References

Details

(Keywords: perf, Whiteboard: [TSnappiness][needs re-triage])

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; pt-BR; rv:1.9.0.4) Gecko/2008102920 Firefox/3.0.4
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; pt-BR; rv:1.9.0.4) Gecko/2008102920 Firefox/3.0.4

After opening the All History window and doing a search there, after I close the history window and starts to open new websites, Firefox hangs for some time while opening that new page(s). This can be checked by trying to scroll down/up while the page is loading. It seems that the history search keeps running after I close the history window and it keeps redoing the search with the new history information I just provided by opening those new pages, as if the history where open with the search yet. Note that this seems to also happen if I just open and close the history window without doing search there, but the hang is very quick (seems that it refreshes the history which would being shown on the screen if the history window were open, but it is not).

Reproducible: Always

Steps to Reproduce:
1. Have a reasonably big browsing history. When you search something in the history, it must take some seconds to show the response (4-5 secs).
2. Having that in step (1), open the "Show all history" window.
3. Type something in the search field.
4. Wait the search to end.
5. Close the history window.
6. Open a new tab and load some page (e.g. www.terra.com.br or www.uol.com.br)
7. Scroll up and down while the page loads. The browser will hang for some seconds and then recover.
8. Restarting the browser ends the problem.
Actual Results:  
Firefox hangs for some seconds, showing the "processing mouse icon" in the screen, and then it recovers and works as expected.

Expected Results:  
Should load the pages without hanging.
Sorry, I forgot to say in the text above (although it is said in the bug title): during the freeze, the CPU usage is around 100%, showing the same pattern as when it is searching the history.
Same bug particular true on linux. I use Firefox a lot and my history accumulates. After 3 day and over hundreds history on first launch ( after reboot my computer (Ubuntu) ) firefox load near 150 Mo of ram !!!!!!

Sometimes when I use the Smart Location Bar, the search continues for long, the ram use is increasing rapidly and process usage turn around 100%.
Hardware: PowerPC → x86
I have the same issue on my WinXP machine.
However, when I disable all plugins it seems to be better.
In the task manager I noticed during the several second-long hangs that CPU utilization was high and that lots of memory were being allocated/deallocated to the firefox process continuously.
have you tried the beta or trunk build?
Severity: normal → minor
Keywords: perf
Version: unspecified → 3.0 Branch
This seems to be a dupe of bug 460593
i think this is due to laying around result from the sidebar, bug 324430 could help there.
Status: UNCONFIRMED → NEW
Depends on: 324430
Ever confirmed: true
Whiteboard: [TSnappiness]
this is probably fixed by bug 324430, needs re-triage.
Whiteboard: [TSnappiness] → [TSnappiness][needs re-triage]
I have tried minefield (oO) and it looks to me like it got better.
After I close the history window, the hangups/slowdowns/de-/allocations seem to no longer be there.
Also tried minefield and seems to be fine. Made the same steps on it and on current version i'm using (Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; pt-BR; rv:1.9.0.11) Gecko/2009060214 Firefox/3.0.11). Current version shown little freezes after closing history window, minefield didn't.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.