Closed
Bug 456647
Opened 17 years ago
Closed 8 years ago
Type ahead find performance degrades for long-lived and much-typed-in tabs loaded via file:/// scheme
Categories
(Toolkit :: Autocomplete, defect)
Tracking
()
RESOLVED
INACTIVE
People
(Reporter: jgold, Unassigned)
References
(
URL
)
Details
(Keywords: perf)
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv:1.9.0.1) Gecko/2008070206 Firefox/3.0.1
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv:1.9.0.1) Gecko/2008070206 Firefox/3.0.1
For reasons I don't understand, after upgrading from Firefox 2 to Firefox 3, I'm noticing that type-ahead find performance degrades when used in a tab loaded with a file:/// scheme in long-lived and much-typed-ahead-in window.
I always load my local copy of Sun's javadocs in a browser while I'm working, and typically do API doc searches 10-50 times a day, always using type ahead find to navigate. If I leave my javadoc tab open for a long time (at this point at least a week), searches eventually bog down and I find myself waiting for the browser to catch up. Closing the tab and reloading seems to fix it, as does loading it via an apache running on localhost and serving the exact same files.
Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Updated•17 years ago
|
Component: General → Autocomplete
Product: Firefox → Toolkit
QA Contact: general → autocomplete
Comment 1•11 years ago
|
||
(In reply to jgold from comment #0)
>...
> If I leave my javadoc tab open for a long time
> (at this point at least a week), searches eventually bog down and I find
> myself waiting for the browser to catch up. Closing the tab and reloading
> seems to fix it, as does loading it via an apache running on localhost and
> serving the exact same files.
>
jgold does this still reproduce? (a week is a tough requirement for reproducing)
Flags: needinfo?(jgold)
Keywords: perf
Comment 2•8 years ago
|
||
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → INACTIVE
Updated•5 years ago
|
Flags: needinfo?(jgold)
You need to log in
before you can comment on or make changes to this bug.
Description
•