XY Often Hangs "Not Responding" on File Rename

[Zardoz2293]

XY = v22.90.0117
Windows 10 Pro (64-bit), 21H2.19044.1620

I've noticed this concern for sometime now. A similar concern exists with thumbnail generation. However, I seem to be encountering the "Not Responding" with greater frequency.

Having a LV with just over a hundred PDF files, perform an F2 (rename file -- single). Microsoft Windows Search Protocol Host process occurs and XY hangs for the duration of SearchProtocolHost.exe on what appears waiting from a Windows Shell CallBack.

You can perform the identical action in WE without any performance hit whatsoever. Usually XY returns after some period, always dependent on the number of files in the folder with the rename event. This time XY never recovered (perpetual "Not Responding").

[highend]

Does this happen in a folder with just over a hundred .txt files (empty ones) as well (and with the same period of waiting time)? What happens if you do this in a folder with file extensions that are not registered (for Windows search to index)?

[admin]

"Having a LV with just over a hundred PDF files..."

LV?

[highend]

Probably "List View"

[Zardoz2293]

"Having a LV with just over a hundred PDF files..."

LV?

ListView

[Zardoz2293]

Does this happen in a folder with just over a hundred .txt files (empty ones) as well (and with the same period of waiting time)? What happens if you do this in a folder with file extensions that are not registered (for Windows search to index)?

It happens whenever Windows Search Host decides to respond the renamed file update. It doesn't happen with each rename, as I'm assuming there is some Windows caching and/or scheduling and when the limit occurs and you perform another rename, then XY will hang until Windows Search Host finishes, well, usually.

I'm assuming it is caused by an XY thread being blocked and having to wait until the (rename) call back finishes (assuming the exit on the rename doesn't return to XY as Windows Search Host hijacks the call forcing XY's thread to wait).

A new thread can be created for the call preventing XY's thread from being blocked.

https://docs.microsoft.com/en-us/window ... ex-objects