Find sometimes doesn't match properly when typing fast in not so small file (but not big either)

[Alexey-T]

Discussed in #5604

^{Originally posted by pintassilgo April 20, 2024}
I downloaded the latest release and tested again the Find with Im, the same test when I reported #5471 (typing "mousepad" in my fast typing speed in a 265k chars file). Now there are no missing chars, but there's a little freezing in Cuda before the word appears in find input, and sometimes the find doesn't work properly.

Document has a single match of "mousepad", but sometimes Cuda state is that wrong: current match is "mou" from one "mouse" word (there are many in the document), while find input is "mousepad" and status shows "Found next match (wrapped, edge-cross, from-caret)". If I press F3, Cuda jumps to the correct "mousepad" match. But I shouldn't need to press F3. Find input is "mousepad", so this word in document must already be the match, not "mou".

Results vary when I try to reproduce. It just happened that "Mousepa" is matched, missing the last "d" char as if find input was "mousepa", but it's not, it's "mousepad". Again, if I press F3 it fixes by including the "d" char in the match.

The screenshot below is similar, but the match is "mousep", missing "ad", but Find input is "mousepad" so it's wrong.

[Alexey-T]

ok, it was a mistake to convert it to a discussion, sorry, I converted it to 'issue' again. new issue was created...

[pintassilgo]

small fix made. any change of find-dlg input causes long search to stop.

beta (linux qt5) cudatext.xz.zip

Still with the same issue. I'll repeat below the steps I use to reproduce, copied from my comment in the original issue, now locked.

Screenshot showing the issue in latest beta, running in a clean Cuda with the steps below:

---

Demo file: bug5473.zip

Originally posted by @pintassilgo in #5473 (comment)

user.json

Steps to reproduce:

1. Use my user.json.
2. Im enabled.
3. Open the txt file.
4. Go to line 3000 (Ctrl+G 3000).
5. Open find bar (Ctrl+F) and type VERY FAST mousepad. If you can't type fast enough it doesn't work. You may need to restart Cuda and try again if you think you might not typed so fast.

You'll see the bug.

My results:
I'm at line 45177 with "mouse" selected in a word "mousepa" (notice the missing 'd', so Cuda shouldn't find this word because I'm searching for "mousepad").

Expected result:
Cuda should be at line 2630 with the only occurrence of the word "mousepad" entirely selected.

Originally posted by @pintassilgo in #5473 (comment)

[Alexey-T]

Thank you for repeating the steps, i already lost them and i need them.

[Alexey-T]

I have idea what to do here. I must disable processMessages which are called to update search progressbar. For small documents.

[Alexey-T]

I had the repro. but with text "12345678" near "mousepad" (and "1234567" near "mousepa") which i can type very fast by moving the 1 finger.

after fix- no repro.

is this better?
cudatext.xz.zip

[pintassilgo]

Seems to be fixed! Thank you.

[Alexey-T]

I found more processMsg calls which to disable. did it. beta2:

cudatext.xz.zip

[pintassilgo]

This one looks good as much as the previous, I no longer can reproduce the issue with them, while I can easily reproduce with previous betas.

[Alexey-T]

you have "find_hi_max_lines": 100000,
so in bigger files, app will still enable processMessages code so some issues may exist! maybe find a time to test smthing with big files.