Closed Bug 269066 Opened 20 years ago Closed 19 years ago

find as you type freezes if search term is not found in page. Does not happen in all installations!!

Categories

(Toolkit :: Find Toolbar, defect)

Product:
Toolkit
Component:
Find Toolbar
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: rlaferte, Assigned: bugzilla)

Details

(Keywords: hang) 

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

If I use Ctrl-F to open the find toolbar, or if the config is set to auto-find
as soon as I type something, results are the same.  On this machine (Compaq
Deskpro with Pentium 3 processor) the problem is that if the search term is not
found because I made a typo for example, Firefox freezes entirely.  Let's say
I'm searching for "About", but I wrote "Aboute"; as soon as I press backspace to
erase the "e" at the end, Firefox freezes.  This does not happen on another
machine on Windows XP.

Reproducible: Always
Steps to Reproduce:
1. Ctrl-F to open find as you type toolbar
2. Type something that's not in the page
3. Enjoy a frozen Firefox! :-)

Actual Results:  
Frozen browser

Expected Results:  
Not frozen browser!

Compaq Deskpro - Pentium 3 processor with 128 MB of RAM.
Windows 2000 Professional v5.00.2195
eTrust anti-virus v7.0.139
I have had this problem for a long time. (Windows XP)  It looks like the windows
freeze is caused by the soundeffect that firefox tries to make when it fails to
find the word you typed.  Windows will freeze for several seconds until the
sound effect is played.

My current solution is to disable the sound effect by setting 

    accessibility.typeaheadfind.enablesound

to false.







(In reply to comment #0)
> User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5)
Gecko/20041107 Firefox/1.0
> Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5)
Gecko/20041107 Firefox/1.0
> 
> If I use Ctrl-F to open the find toolbar, or if the config is set to auto-find
> as soon as I type something, results are the same.  On this machine (Compaq
> Deskpro with Pentium 3 processor) the problem is that if the search term is not
> found because I made a typo for example, Firefox freezes entirely.  Let's say
> I'm searching for "About", but I wrote "Aboute"; as soon as I press backspace to
> erase the "e" at the end, Firefox freezes.  This does not happen on another
> machine on Windows XP.
> 
> Reproducible: Always
> Steps to Reproduce:
> 1. Ctrl-F to open find as you type toolbar
> 2. Type something that's not in the page
> 3. Enjoy a frozen Firefox! :-)
> 
> Actual Results:  
> Frozen browser
> 
> Expected Results:  
> Not frozen browser!
> 
> Compaq Deskpro - Pentium 3 processor with 128 MB of RAM.
> Windows 2000 Professional v5.00.2195
> eTrust anti-virus v7.0.139


So, Robert, does the workaround from comment 1 help?

ringer9cs@gmail.com: any other programs have the same problem? Tried installing
newer sound drivers / reconfiguring sound card/chip?
Keywords: hang
OS: Windows 2000 → Windows XP
My computer has many applications that play sound: itunes, foobar, flash
players, movie players, etc.  No other programs have the same problem. 
Everything is fine except the Firefox find-as-you-type bar.

I am using an IBM X31 laptop with Windows XP Pro preinstalled.  The sound driver
is up-to-date.

(In reply to comment #2)
> ringer9cs@gmail.com: any other programs have the same problem? Tried installing
> newer sound drivers / reconfiguring sound card/chip?

does setting accessibility.typeaheadfind.soundURL -> beep help?
Yes! It worked.  I set it to file:///C:/WINDOWS/Media/ding.wav and it worked. It
sounds right.  No hang-ups any more.  I set it to other wav files and firefox
also worked.  If I set it to a wrong URL like "file:///C:/WINDOWS/Media/",
firefox will not make any sound but it does not hang up.  

(In reply to comment #4)
> does setting accessibility.typeaheadfind.soundURL -> beep help?


(In reply to comment #0)
I face exactly the same problem, particularly in heavy pages (ex. 500 Ko)
All Mozilla windows freeze for several seconds.

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/

(In reply to comment #2)
> So, Robert, does the workaround from comment 1 help?
> ringer9cs@gmail.com: any other programs have the same problem? Tried 
installing
> newer sound drivers / reconfiguring sound card/chip?


Yes it works, sorry for the absence of reaction, I've been using another 
computer where the bug is not present.

Bob

(In reply to comment #8)
> (In reply to comment #2)
> > So, Robert, does the workaround from comment 1 help?
> > ringer9cs@gmail.com: any other programs have the same problem? Tried 
> installing
> > newer sound drivers / reconfiguring sound card/chip?
> Yes it works, sorry for the absence of reaction, I've been using another 
> computer where the bug is not present.

Forgot to add, I've updated the "offending" computer to the latest release 
(1.0.7) and the bug doesn't seem to be there anymore...

Bob
(In reply to comment #9)
> 
> Forgot to add, I've updated the "offending" computer to the latest release 
> (1.0.7) and the bug doesn't seem to be there anymore...
> 

-> WORKSFORME
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.