Incorrect behaviour of Find Files dialog

[browny]

Windows 11, TC 11.03 64-bit.
Searching for directories that were recently modified (for purging older subdirectories with stale data).
The procedure is performed rarely, but is more or less a known routine.
At some point I noticed that search results are odd and sometimes just empty (while there should have been found entries).
Then I tried to play with search options, and came to conclusion that internal search parameters differ from the ones in dialog.
This was not studied very deeply, a trivial TC restart was applied and things returned to normal state.

Never noticed anything like that, and again non-reproducible behaviour.
However, recalling another rare issue with stuck "Show" buttons in Sync tool, both might be cases of memory corruption.

PS. Forum notifications list refused to clean up, and now it is empty. Thanks.

[Hacker]

browny,
That does not really give us much to go by.

Roman

[ghisler(Author)]

Do you use "Everything" for searching? When using the ev: prefix, the search syntax is indeed different from the internal syntax. Then Total Commander uses the "Everything" syntax. Also when indexing folders, the info in "Everything" can lag a few seconds. For example, when I delete all files in a directory, "everything" will still report the old directory size for a few seconds.

[browny]

Do you use "Everything" for searching?

No, never tried it and even do not know how it looks.
Directory contents was not changing while searches were performed; data should have been already on disk - less than an hour, but surely longer than several seconds.

[petermad]

2browny

came to conclusion that internal search parameters differ from the ones in dialog.

Could you give an example of what you mean by that?

[browny]

petermad,
Empty search results was already mentioned.
When searching in the current directory only, there were at least two more levels in results.

[petermad]

2browny
I was curious: what do you mean by the phrase "internal search parameters"?

[ghisler(Author)]

2browny
Could you give an example of the search terms you use, and which name isn't found although you think it should be found?

[browny]

Directories not older than 1 hour.
Search for was either empty or *.pdb
Depth could be unlimited, current directory or 1 level.

[petermad]

Directories not older than 1 hour.
Search for was either empty

Works as expected here.

This was not studied very deeply, a trivial TC restart was applied and things returned to normal state.
Never noticed anything like that, and again non-reproducible behaviour.

Have you encountered this behavior since then?

[ghisler(Author)]

Directories not older than 1 hour.
Search for was either empty or *.pdb

If you search for attribute "directory" and *.pdb, you won't find anything, unless the directories themselves have the .pdb extension.

[browny]

If you search for attribute "directory" and *.pdb, you won't find anything, unless the directories themselves have the .pdb extension.

In the current directory all directories had .pdb extension, and there were no *.pdb directories at lower levels.

[ghisler(Author)]

That should work fine. I have tested it by renaming a directory to test.pdb and using Files - Change attributes to change the timestamp to the current date and time. Are you sure the directories were not older than 1 hour?

[Hacker]

Could this not be the "I deselected every Attribute except for Directory" mistake?

Roman

[browny]

It seems some trivial points are misread all the time.
This behaviour was seen only once.
Search was doing fine before the event and right after restart.
TC is usually running for hours and days before anything weird happens, then it is impossible to guess what was the trigger.

Could this not be the "I deselected every Attribute except for Directory" mistake?

How this explains that more than one level of directories were in the list when searching at the current level only?
To add more fun, there are also *.pdb files in subdirectories.