Closed
Bug 621935
Opened 14 years ago
Closed 14 years ago
Searching in bookmarks or history shouldn't block the whole browser
Categories
(Firefox :: Bookmarks & History, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 595530
People
(Reporter: mgol, Unassigned)
Details
Attachments
(1 file)
2.53 KB,
text/html
|
Details |
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101206 Ubuntu/10.04 (lucid) Firefox/3.6.13 Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101206 Ubuntu/10.04 (lucid) Firefox/3.6.13 Searching in bookmarks or history blocks the whole browser which makes user experience extremely annoying. I consider it a critical issue as sometimes the browser blocks so strongly that the only solution is to kill the Firefox process so this could lead to data loss. Reproducible: Always Steps to Reproduce: 1. Click on the history button in the Navigation Toolbar 2. Search for a short word Actual Results: The browser locks for a long time Expected Results: The browser shouldn't be locked even for a fraction of second, search should be done in a separate thread and it shouldn't block the whole browser.
Reporter | ||
Comment 1•14 years ago
|
||
Updated•14 years ago
|
Whiteboard: DUPEME
Comment 2•14 years ago
|
||
calling this a dupe of bug 595530 since that bug is what makes things worst.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 3•14 years ago
|
||
Should it really be a duplicate? Maybe it is indeed the main reason for the browser lock-up but I am suggesting separating the search function by putting it in a separate thread. Fast search could be fast but it will still lock the browser up.
Comment 4•14 years ago
|
||
there are other filed bugs for async queries, so it's just matter of choosing a dupe, but the final result doesn't change.
You need to log in
before you can comment on or make changes to this bug.
Description
•