Closed Bug 210004 Opened 22 years ago Closed 20 years ago

backspace in typeaheadfind freezes mozilla for 30 sec on large file

Categories

(SeaMonkey :: Find In Page, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: kruppa, Assigned: aaronlev)

References

()

Details

(Keywords: perf)

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030617 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030617 On the page http://www.loria.fr/~zimmerma/records/c120-355 , which is a text file of 706890 bytes, hitting the Backspace key during a typeaheadfind freezes Mozilla for about 30 seconds. The text typed so far must be found in the page, i.e. "2," (without the ""). Reproducible: Always Steps to Reproduce: 1. Load mentioned URL into Mozilla 2. Type "2," and press backspace key Actual Results: Mozilla does freezes for about 30 seconds, then prints "Find stopped." in the status bar. Expected Results: Find the first match of the shortened search term (i.e. "2") and respond more quickly.
Keywords: perf
Works for me Mozilla Firebird 0.7+ Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031108 Mozilla Firebird/0.6.1
I've been having freeze problems on PC version of Netscape 7.1 too. Perhaps it's related to the nsSound? See converstaion on bug 210209.
I doubt it. I don't have any "audiofile" package installed, and this bug doesn't freeze Mozilla solid as the audiofile bug does, but freezes it only for a certain time. I much rather believe that the very frequent occurance of the sting "2" in the test case text makes the search code spend a long time looking for matches of the shortened string.
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
Bug is gone in newer releases. Closed as FIXED.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
No specific bug / patch referred to as the fix. -> WORKSFORME
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago20 years ago
Resolution: --- → WORKSFORME
Product: Core → SeaMonkey
You need to log in before you can comment on or make changes to this bug.