Strange main window and log behavior on 0.4.9.9h, errors in log console

[ShadowVolt]

I'm having some strange behavior with version 0.4.9.9h. (I made sure it was reproducible on my machine before reporting this, but knowing how bugs work, this will somehow magically solve itself on its own later lol.)

After some time using the program, the main window appears to get out of sync with the logs, and slowly moves to the more recent lines over time (without any new inputs) instead of staying in sync. At the same time this is occuring, the script-match drop down completely stops working on new lines in the log until the program is rebooted. The lines from before the glitch starts still work though. If I wait until it completely catches up, the drop down starts to work for a short time, then it stops again as new lines come in.

To my untrained eye, it almost looks like it is script-matching at the exact moment the OCR line comes in, even before the main window has a chance to update. Maybe it's matching so fast that the internal logic breaks somehow, forming some kind of loop? Just wildly speculating here, I'm likely quite wrong about that one. (this only started after updating to a version since regional matching was added, have been on a slightly older build until now.)

But in any case, every time this happens it throws this error in chrome's console in the log page (specifically the first one, included the second since it may be relevant despite only happening once. I haven't touched the anki part in this install.):

---

(Additional info: This is a clean install, aside from the game script. The only non-UI setting I have changed is "match_limit" from the default of 5 down to 2.)

[mathewthe2]

I haven't checked yet, but there could a race condition issue with script match updating the main window while the OCR goes in, or it could be a completely different issue.

[mathewthe2]

Are you able to recreate this issue with minimal amount of matching?

[ShadowVolt]

Yes. After doing some testing to find what triggers it, I found a way force it to happen. Trying to match very quickly using a game script seems to do the trick. (The line has to be in the script/be able to match, and I haven't tested with the feature off.) I have it on a hotkey with a preset scan region, with that setup just scan the same line again as soon as you see it pop into the log, and it will happen within thirty seconds to a minute of matching.

This is still happening on a clean install of 0.4.9.9i, and it's making it hard to use this program, since every time it happens I have to reboot it. (for the moment I have moved back to a working build) Unfortunately I don't have another machine to test it on, so I have no idea if it is hardware or OS specific or something.

(Pardon the late reply, have been away for the last couple days.)

[ShadowVolt]

Had some time to poke around at this more, and it seems that this bug was introduced in version 0.4.9.9e, since I can't make it happen on builds 9d and older. Even mashing the hotkey more than 20 times as fast as I could didn't faze it at all (which basically always triggers it on the newer builds.)

Not completely sure where build 9e lines up here on github, but 9d was the first build that had the log limit and min match feature. (which works correctly in 9d, so that wasn't the cause.)

But for the record in this issue; I'm on windows, specifically a preview build of windows 10 (21H2). Some time after I've posted this when I get more time to test, I may try this on a different windows version to see if that somehow changes anything. (Can spin up a VM to test, but will take some effort and time to do, so it will be a bit)