Awesomebar gets slower the longer Firefox is open

RESOLVED INCOMPLETE

Status

()

--
major
RESOLVED INCOMPLETE
10 years ago
8 years ago

People

(Reporter: magicrisco, Unassigned)

Tracking

3.5 Branch
All
Windows Vista
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

10 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1b4pre) Gecko/20090415 Shiretoko/3.5b4pre (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1b4pre) Gecko/20090415 Shiretoko/3.5b4pre (.NET CLR 3.5.30729)

With the latest nightlies, awesomebar gets slower the longer you keep firefox open. It slows down after about a minute of use.

Reproducible: Always

Steps to Reproduce:
1. Open Firefox, type something in awesomebar.
2. Very fast.
3. Do a bit of surfing.
4. Type something in awesomebar.
5. Slow retrieval of results.
Actual Results:  
Slow retrieval of results.

Expected Results:  
Should be pretty much instant.

Updated

10 years ago
Component: Bookmarks & History → Location Bar and Autocomplete
QA Contact: bookmarks → location.bar

Comment 1

10 years ago
to me the popup opening looks a bit slower, not the search itself. if this has regressed recently can anyone find a regression range (or a date where the issue has started).
Is this Vista only? Since that code has not changed recently could be a slowdown in painting the popup (due to Bug 376408 maybe?)

Comment 2

10 years ago
WFM in Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2a1pre) Gecko/20090416 Minefield/3.6a1pre (.NET CLR 3.5.30729) ID:20090416042608. There is a tiny bit f slow down on very long result lists, but not much. Does it happen in safe mode or a new profile?
Version: unspecified → 3.1 Branch
(Reporter)

Comment 3

10 years ago
It does not happen from what I can tell in a new profile, but is because I have no history to search so is naturally faster. Trying to find a regression range, but it is proving very hard.

Comment 4

10 years ago
I think this started at 20090415, around the time of the autocomplete crash issue.

I thought it was because I disabled Autocomplete, but it might be this issue instead.

Comment 5

10 years ago
(In reply to comment #4)
> I think this started at 20090415, around the time of the autocomplete crash
> issue.
> 
Karl, Leman, can you guys save your profile in a safe place (just to be on the safe side) and then try finding a regression range for this by using old builds on your normal profile?

Comment 6

10 years ago
what extensions do you have active?
Do you use Google Toolbar by chance?
Anti antivirus with check pages option?
(Reporter)

Comment 7

10 years ago
Hi, real sorry to open the bug then appear to not bother searching for a regression. I had a lot of stuff on at work. I will have a look tonight to see where the issue is.

To Marco - I use NOD32 Version 4 with default settings, no page check option. I also do not use google toolbar.

My extensions are as follows:

Adblock Plus
Glasser
Stylish
Download statusbar
Downloadthemall
Personal Menu
Nightly Tester Tools
Yet another smooth scrolling
Toggle private browsing

Comment 8

10 years ago
Make sure to try in safe mode to make sure those extensions are not causing it.
(Reporter)

Comment 9

10 years ago
Ok I believe I have narrowed it down to between 11th and 12th April Builds. Trying to narrow down to the correct hourly.

Comment 10

10 years ago
(In reply to comment #9)
> Ok I believe I have narrowed it down to between 11th and 12th April Builds.
> Trying to narrow down to the correct hourly.

Karl, were you successful?

Comment 11

10 years ago
The Awesome Bar seems to open up almost immediately, and I have a lot of bookmarks. 

Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2a1pre) Gecko/20090714 Minefield/3.6a1pre
Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode? If not, please close. These links can help you in your testing.
http://support.mozilla.com/kb/Safe+Mode
http://support.mozilla.com/kb/Managing+profiles
The bug is too generic to do any useful stuff, and missing information on reproduceability on 3.6 and 4.0.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.