minor(?) glitch/inaccuracy when searching webpage text

[mortalwombat]

windows x64, PM 28.4.0, keyboard refresh rate set to maximum of about 30 hertz.
on any page with a good amount of text, like, a few pages of text or more, hit control-F to search for a common character like "a" or "e", which will appear hundreds of times on the page (over 100, but preferably not over 1000, because apparently that is the limit on matches that PM will report that it found), and it will highlight a first result, as normal, and will display something like "1 of 847 matches", as normal, but something abnormal will happen if you hold down the F3 key, to quickly cycle through all the results, each highlighted one by one at a rapid speed, with Windows keyboard refresh rate maxed out around 30 hertz; then the "847" somehow/somewhy changes to a smaller number which is always a multiple of 100, like for example "1 of 500 matches", "1 of 700 matches", "1 of 600 matches", etc. you can sit and watch it skip through multiples of 100. then if you let go of F3, I think it always corrects itself back to "847", but I'm not sure if it's always or just sometimes. then if you just hit F3 again only once, it will always correct itself back to "847". holding down F3 again, it'll go back to unpredictable multiples of 100 again, instead of the correct number of "847".

[Moonchild]

This is an unfortunate side-effect of asynchronously updating these statistics. The high speed of repeated searches can, in such a case, fire off a new search while the update would still be in progress (and counting a large number of matches simply takes some computing time) and therefore "skip a beat". The count update will then be inaccurate as a result. With the current implementation of the findbar, this is unavoidable.