Closed
Bug 661368
Opened 14 years ago
Closed 14 years ago
Awesomebar stops returning results; browser then hangs when closing
Categories
(Firefox :: Address Bar, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 684513
People
(Reporter: josh, Unassigned)
Details
Currently running Firefox 6.0a2 ("Mozilla/5.0 (X11; Linux x86_64; rv:6.0a2) Gecko/20110525 Firefox/6.0a2"). I've encountered the following bug repeatedly. At some point during a browser session, the awesomebar will stop returning results as I type; the spinner on the left will keep spinning, but the dropdown of results never displays. Once this has happened, if I subsequently close the browser, the firefox-bin process will stick around and not close, and attempting to start the browser again will bring up the dialog saying to close the existing instance of Firefox first. To recover, I have to killall firefox-bin before starting the browser again.
Reporter | ||
Comment 1•14 years ago
|
||
Further information: Once the browser gets into this state, opening the history (Ctrl-H) and searching there causes the browser to hang completely and use 100% CPU.
Reporter | ||
Comment 2•14 years ago
|
||
I found a procedure that seems to reliably reproduce this bug. If I type a string which matches some results, the awesomebar will return those results near-instantly, as usual. If I type a string which does not match any results (whether gibberish or just a typo), the animated spinning icon starts spinning, and no results come back. For the rest of that browser session, any attempt to use the awesomebar will produce no results, and continue to just show the spinning icon.
Comment 3•14 years ago
|
||
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:7.0a1) Gecko/20110531 Firefox/7.0a1 ID:20110531030222 WFM - possibly linux only or already fixed in trunk.
Reporter | ||
Comment 4•14 years ago
|
||
Merging into 684513, which I reported without remembering this bug; however, 684513 has much more detail.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•