Hi Jean,
I got again issues of QAP not responding, or more precisely, responding very very slowly.
I already had the problem in the past, and we already discussed it.... but with no solution.
Since it re-occured these days, I have a little bit investigated, and I think I have (at least partially) understood the problem (and I hope you'll understand how to fix it

).
Actually, it occurs
while QAP is udating the QAP_Frequent.DB... that takes a long time ((typically
up to 20 or 30 seconds) when database is "relatively" big.
And since the update takes such a long time, there is serious probability that we try to use QAP during this time... which makes the problem visible.
How did I run my test :
1) I first change the parameter UsageDbIntervalSeconds to a small value (let's say 10 sec) to force frequent update.
2) Thanks to QAP, I open a folder not opened for a long time
3) I reopen QAP menu immediately after, and the folder I just opened in 2) is not (yet) in "Recent Folders"
4) I wait just a little bit more than the duration set in 1), let's say 12 seconds
5) I try again to open QAP menu.... and it's unsuccessfully : QAP is not responding. I repeat trying to open the menu until it opens.
6) Next time it opens, "Recent Folders" contains folder open in 2), and we can see in explorer that database file has just been updated.
If I stop QAP / delete the database / restart QAP, a new DB is created , a lot smaller, and repeating the process above,
DB update is fast enough to never make QAP unresponding. But of course, I have lost "Frequent folders" and "Frequent files" (but "Recent" ones are still there....)
Several remarks now :
- When I say "big" databse, this one was around +/- 1Mb, +/- 2500 lines in Usage table
- I tried to "compact" the database thanks to "DB Browser for SQlite" application : no advantage
- I tried also to remove oldest lines in Usage table, reducing the database approx. by half, but this didn't change anything to the problem.
- Actually, it is not feasible to put a value less than 60 seconds to UsageDbIntervalSeconds in the GUI, but feasible updating manually QuickAccessPopup.ini file. I agree that such a small value is surely not a good idea in normal life, but it helps a lot to run the process above without waiting too long between steps...
- When QAP is not responding, it is not only the display of the menu that is not responding : right click on QAP's icon in tray do not opens the "system" menu...
- I tried to set the DiagMode in QuickAccessPopup.ini, but almost nothing is logged in QuickAccessPopup-DIAG.txt (contrary to previous versions of QAP)
And finally one "suggestion" : Is it the same thread that updates database and manages the menu ? If yes, wouldn't it be feasible to have Db update "delegated" to a separate thread ?