XYplorer Beta Club

Is the stale cache issue maybe related to the use of View | Tab | Relocate Tab...?

I've never used that function. Not even once.

Currently out of ideas. Cannot reproduce these issues.

It's definitely (at least) a caching issue

With Configuration | Find and Filter | Find Files & Branch View | Find Files | Cache search results
unticked

it doesn't happen anymore...

The interesting thing is: It doesn't happen when I startup my configured instance

I do normal file management tasks, switch tabs, folders, do searches, start scripts, etc., yaddayadda and (maybe) then I can reproduce the issue

I normally only restart my instance on an XY upgrade and I only use it as a read-only clone

And regarding the unticked cache search result (I've did this while I didn't restart it and the issue immediately went away)

I fixed a couple of related glitches now. Let's see what happens.

Well I get blank QS tab now always .0316 when tab switching (even non multi-loc QS), here is an example slog:

• Line 1 is the original multiloc quicksearch (but now happens with single folder QS too)
• Line 2 tabswitch (to a normal non QS tab)
• Line 3 tabswitch back to QS tab
• Line 4 Result = 0 items now for the same Line 1 QS tab

In my normal config it is 100% reproducible every tab switch with cache enabled, disable cache and all works as expected. I guess I will have to live without QS cache.

Here is an example (not from same event as above slog) of a single folder basic QS and tab switch:

Can you show the address bar as well? Then I can even see the search pattern.

I haven't the slightest idea what could be causing this.

Could you show a screenshot of Configuration | Find and Filter | Find Files & Branch View?

Or maybe your tabset is somehow corrupt.
Well, unlikely with just two tabs...

In the next beta, when you hover the caption part of a tab header and hold SHIFT, the tooltip will give you the path to the tab_*.ini file where the cache data is stored. You can check then whether this file actually has the cache data.

I could send a screenshot if you really want, but I have fiddled with all those settings for hours trying to repro in fresh so they aren't relevant, but anyway, I am confident that I just worked out the cause. Since all the recent QS issues sprung up that I mentioned earlier in this thread, I have been doing all my testing in a RO instance because I was trying all sorts of things, anyway based on your last comment I realized that the QS cache isn't in RAM, it is on disk immediately (I'd never checked), which doesn't happen in a RO instance, and depending on the tab number of the QS tab, it reads from the stale cache of the non-RO instance for that tab number, that explains why I got different results sometimes, and it also theoretically explains why sometimes I get the path column with chars trimmed from front, I assume that it trims c:\test (the AB path) char count from c:\whatever folder which becomes "ever" in relative path column (when wrong files from wrong path added to list from different cache).

I guess, if it is feasible, the obvious solution to this issue would be auto disabling QS cache in RO mode, unless you can think of a better alternative.

Ah, you got it!

jupe wrote: ↑18 May 2022 23:31 I guess, if it is feasible, the obvious solution to this issue would be auto disabling QS cache in RO mode, unless you can think of a better alternative.

Yeah, I think that's the way to go.

Is there no way to do this in ram instead or in a tmp file (for ro-instances)?

In theory a lot is possible. And XY went the way it is now.

Cool! Then... make it possible

I only use XY in ro-mode, a never changing version, like fresh but fully configured.
But uncached searches are a big letdown...