After upgrading to 6.3.0.17, sporadic access violation using Quick Search

[cnewtonne]

Thank you.
Downloading the latest release still shows 'UltraRecall.exe version 6.3.0.17'. I see same behavior. UR aborts when duplicating a QS tab with search edit box contains a search string.

I have not tested with a sample urd db. I did test three different database. UR crashes on all three. I'll try to test with a sample db.

You are also correct in that version .16 does not have the AND column but continues to crash.

One consistent pattern I see is that crash occurs only when duplicating QS tab when the search edit box contains a search string. If I remove the string, UR does not crash.

[kinook]

Try clearing your browser cache and re-downloading, then uninstalling and installing. It will show 6.3.0.18 in Help | About if you have the latest version.

[cnewtonne]

I was able to produce a crash/abort using .18 release.

I went back & examined the release history changes as documented by Kinook. Starting from the 'fact' that release .12 did not crash while .17 and .18 did.

For the enhancement section, releases jump from .12 to .17. An enhancement which is supporting AND/OR in QS. We ruled this out as the cause of the crash because .16 didn't have it, but it crashed.

For the 'bug fixes' section, there is no .12 release listed, but, a bug fix in .13 which seems unrelated (combining text). There is search related bug fix and behavior change introduced in .15 regarding SearchNonAsciiTextNonCaseSensitive.

With this is key set to zero, I was NOT able to crash .18 or. 17. Deleting the key, I was able to crash both releases. I mean duplicating QS a 100 times, did not crash it. Just similar to what I experienced in release .12. I never was able to do 100 QS tabs without a crash.

I'll be using UR for the next few days. I was getting crashes daily last week. I'll confirm again.

[kinook]

Thank you, that helped narrow things down. I was finally able to identify the issue and it's fixed in v6.3.0.19.

[cnewtonne]

Wow!
So rewarding to see the word 'fixed'. Testing with .19, I ran the same test of generating near 100 QS tabs with and without string string, no crash. Looks good.

I'll confirm as I continue to use UR for the upcoming days.

Of course, it is not typical of my workload to generate this many QS tabs all at once. But, in the course of a day, I probably do.

Thank you.

[cnewtonne]

It has been three days now without any crash or AV errors. I used to get them daily last week.
Looks like the issue is now resolved in release *.19.

Thanks for the great support.