803579 - Firefox saturates CPU and stops responding when doing text search

Status: RESOLVED DUPLICATE of bug 804799

(Core :: Find Backend, defect)

Description

[David Smith]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:19.0) Gecko/19.0 Firefox/19.0
Build ID: 20121019030551

Steps to reproduce:

On page: http://arstechnica.com/information-technology/2012/08/firefox-continues-to-gain-as-internet-explorer-chrome-slide/?comments=1&start=40#comments-bar

Attempt to do a find-as-you-type text search (hit /, start typing).

Have not encountered the problem on other sites, though testing for that is fairly limited.


Actual results:

Firefox completely locks up, saturating one CPU.  Have to force-terminate using task manager.

Attempted to retest with: each individual addon disabled (progressively tested through all the ones I have installed), all plugins disabled, graphics acceleration turned off, and in safe mode.  Problem occurred in all cases (though it did not lock up in one instance of safe mode, it did lock up in a later instance).

Problem was replicated by another user on Mozillazine forum (10/20/2012 build thread).


Expected results:

Search should have worked normally.

Comment 1

[Jim Jeffery not reading bug-mail 1/2/11]

No hang/lockup here
Win7 x64 AMD HD3200 GPU-chip on mobo, Athlon Phenom II CPU 8 gig ram 

latest hourly build win32 m-c cset: 
https://hg.mozilla.org/mozilla-central/rev/7fcac3016159

Comment 2

[Spencer Selander [greenknight]]

I get lockup on XP x86 SP3, Sempron 3400+ 2GHz (single core), 2 GB RAM, latest Nightly:

Mozilla/5.0 (Windows NT 5.1; rv:19.0) Gecko/19.0 Firefox/19.0 ID:20121018030618

Comment 3

[IU]

Fixed for me with today's nightly build: http://hg.mozilla.org/mozilla-central/rev/ff4af83233dc

David, please confirm whether the bug is also gone for you, with the Sept 20 nightly build.  Resolve WORKSFORME, if you can confirm.

Comment 4

[David Smith]

Sorry, no.  It still locks up with today's build.

Comment 5

[IU]

Regression range: http://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=78c16f313547&tochange=2efb9e5762ce

Caused by bug 773247

Comment 6

[Boris Zbarsky [:bzbarsky]]

Patch in bug 804799 will fix this.