Closed Bug 833781 Opened 13 years ago Closed 13 years ago

Firefox freezes after clearing page search by backspacing and then typing one character.

Categories

(Firefox :: Untriaged, defect)

18 Branch
x86_64
Windows Server 2003
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 773247

People

(Reporter: atmcdo, Unassigned)

Details

(Keywords: hang, perf)

User Agent: Mozilla/5.0 (Windows NT 5.2; WOW64; rv:18.0) Gecko/20100101 Firefox/18.0 Build ID: 20130116073211 Steps to reproduce: I load the following page http://zenwerx.com/projects/pi-digits/pi/ then I do a search for a number (like a phone number) on that page using Find: at the bottom of the window. Then I backspace until the Find: text block is empty and the cursor is blinking. Then I type a single number and Firefox freezes. The number does not show up and the cursor stops blinking. I have to kill the application using Windows Task Manager. You may have to do a few searches before it happens. This is on Firefox 17 and 18.0.1. It also happens in safe mode. Actual results: Firefox freezes. The cursor stops blinking. I have to kill the application using Windows Task Manager. Expected results: Should have searched the page as it normally does, shown number typed and had cursor flashing after number typed.
Same here, Firefox is not responding during the 2nd search.
Keywords: hang, perf
WFM over here with Mozilla/5.0 (Windows NT 6.1; WOW64; rv:18.0) Gecko/20100101 Firefox/18.0 ID:20130116073211 and Mozilla/5.0 (Windows NT 6.1; WOW64; rv:21.0) Gecko/20130123 Firefox/21.0 ID:20130123052720 Does it happen with Flash explicitly turned off?
I tried again with FF21, it worked fine. Weird.
(In reply to Loic from comment #3) > I tried again with FF21, it worked fine. Weird. dupe of bug 773247 ? Reporter: Could you try Firefox19beta and look if it's fixed there ?
(In reply to Matthias Versen [:Matti] from comment #4) > (In reply to Loic from comment #3) > > I tried again with FF21, it worked fine. Weird. > dupe of bug 773247 ? > > Reporter: Could you try Firefox19beta and look if it's fixed there ? Yes, it's a dupe of bug 773247, good catch. It's fixed in FF19+ indeed: m-c bad=2012-10-12 good=2012-10-13 http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=1301a72b1c39&tochange=90857937b601
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.