Quick Filter Bar search delay should be longer or configurable (premature search on unfinished word takes long in big folders)
Categories
(Thunderbird :: Search, defect)
Tracking
(Not tracked)
People
(Reporter: u491341, Unassigned, NeedInfo)
References
(Depends on 1 open bug)
Details
(Keywords: perf, Whiteboard: [needs profile])
Updated•11 years ago
|
Updated•11 years ago
|
Comment 1•10 years ago
|
||
Comment 3•10 years ago
|
||
Comment 7•8 years ago
|
||
Comment 8•8 years ago
|
||
Comment 10•8 years ago
|
||
Comment 11•8 years ago
|
||
Comment 13•8 years ago
•
|
||
Comment 16•4 years ago
•
|
||
I reported bug 1649973, sorry for the duplicate.
This is a better description of the performance issue than I wrote in frustration last night.
I think there should be a button to begin the quicksearch, and no effort to notice what was typed in the search terms should be noticed until that button or a return is pressed.
Updated•4 years ago
|
Comment 17•4 years ago
|
||
There ought to be a stop searching button with the start searching button to begin the quicksearch.
If you use a term that is common the search can be very time consuming and there is no way to stop it, especially if you have many messages.
I had to use taskmanager to stop the Thunderbird process after 5 minutes. I had found what I was looking for but the search could not be stopped and the rotating wait indicator was rotating. This is a waste of time. Windows 10. Thunderbird 68.7.0 (32-bit)
I wasn't able to find a 64 bit version when I looked. Does one exist?
Comment 18•4 years ago
|
||
This seems to me to have been fixed years ago and now it's back. I guess somebody has shortened the delay between when the user starts typing their string and when search commences. Again? If you find it please comment it nice and big so someone doesn't do it yet again. Thanks
Comment 19•4 years ago
|
||
(In reply to Steve from comment #17)
There ought to be a stop searching button with the start searching button to begin the quicksearch.
Just edit the quick search field and blank it out?
(In reply to steve hayes from comment #18)
This seems to me to have been fixed years ago and now it's back.
Nothing in the code has changed recently.
Comment 20•4 years ago
|
||
Thanks for the speedy reply.
Maybe there's an interrupt on a keypress which has been altered? I don't know, but I am utterly certain that this was a problem, then it was fixed, and now the same symptoms/problem is back, and it really is a problem, 10s of seconds lost multiple times a day
I have a small screen recording on https://photos.app.goo.gl/nnyn8qCC5a9DGXx1A
Comment 23•3 years ago
|
||
This serious bug has been languishing for eight years. I just posted a duplicate in frustration. I didn't remember the last time.
Updated•2 years ago
|
Comment 24•17 days ago
|
||
Version 128 does have an increased delay. Does it perform well for you?
Description
•