Closed Bug 606995 Opened 14 years ago Closed 13 years ago

Having the global history window open (especially with a search term) massively impacts general browsing perf

Categories

(Toolkit :: Places, defect)

x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 556068

People

(Reporter: davida, Unassigned)

Details

(Keywords: perf)

STRs:

1) using an old profile w/ lots of data (my places.sqlite is 50M)
2) go to History | Show All History
3) in search field, type 'etherpad' (which in my case shows a fair number of entries

From now on, at least navigating to a page that has etherpad in the URL results in a beachball and a 3-second hang.  

4) close history window

no more beachballs and hangs.
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0b8pre) Gecko/20101023 Firefox/4.0b8pre
Whiteboard: dupeme
So, in current nightlies we suffer of bug 595530 that makes all history searches damn slow.  This is fixed on Places branch so you could the latest build labeled "places-XXXXX" and try that.  If the issue is solved this is a dupe of bug 595530.

Otherwise I'd say this is a dupe of bug 556068. We have some work ongoing to improve the situation but it's the global notifications system to the ui that is slow, even if the library is in background or minimized we keep updating the search, if the search is slow everything becomes sluggish.
Component: History: Global → Places
Product: Core → Toolkit
QA Contact: history.global → places
notice, don't use places build with your profile, make a new testing profile or backup places.sqlite before using the build and restore it later.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Whiteboard: dupeme
You need to log in before you can comment on or make changes to this bug.