"Move Up" w collision rename crashes XY (x64)

[Malarki]

XY 64-bit v27.90.0021 on Windows 10 x64

Setup is a Parent folder with a Child folder; both with the same file in them:

PARENT\
...file.txt
...CHILD\
......file.txt

#) While in CHILD I select file.txt and apply the right-click command "Move Up".

#) I get the "Replace or Skip Files" dialog in which I select "Compare info for both files".

#) I get the "1 File Conflict" dialog in which I checkmark both "Files from Child" and "Files already in Parent". So I expect a suffix rename of the file being moved.

#) When I click on "Continue", I briefly see the file ops progress window then XY crashes.

Performing a manual Move doesn't have this issue. In my testing XY crashes only when its "Move Up" is used.

[LATER EDIT - SEE FURTHER INFO BELOW]

Here are my Config File Ops settings:

CAP_ 40708.jpg (157.16 KiB) Viewed 1172 times

[Malarki]

FURTHER INFO:

A fresh:: instance does not have this problem until I tick "For cross-volume moves only" which is by default unticked.

When this option is unticked, the XY Custom Move is used and works fine. With it ticked (as in my Config settings above) the Windows Move is apparently used instead, which somehow leads to the crash.

Later... I notice that "No progress dialog on intra-volume moves" is ticked. Yet in my case, Windows Move is trying to show a progress bar for a moment before the crash. Maybe that's related.

[admin]

Oh, yeah, that's a very good bug. It led to a morning of work and a number of improvements to Shell Copy/Move.

[Malarki]

Great, and I confirm that the above problem is gone in the 0022 beta. I'm sure that will fix the occasional crash I've had with XYTB when moving or copying files had a collision. Those were confusing and I couldn't begin to replicate them, but this "Move up" was repeatable.