XYplorer Beta Club

hansmuff wrote: ↑17 Nov 2020 18:29 Update:

The issue persists with the latest Beta using my current configuration.

I will describe what exactly I'm doing:
I have a folder C:\den\config
I have another folder C:\Repo

C:\Repo holds a git repository, it's a large Visual Studio project.
C:\den\config holds project files I have to customize on my machine, as compared to what's in the remote Git repository

So, when I get a new branch from the remote, it'll overwrite my project files in C:\Repo.
So I'll go into C:\den\config, hit CTRL+A, CTRL+C, then change panes (i use dual pane) to C:\Repo and hit CTRL+V.
I get a question whether I want to merge directories, to which I say Yes and "Do this also for the next collisions"

Now we get to the meat of this:
I get a message that the files already exist and what I want to do, and I'll say "Overwrite" and "Do this also for the next collisions"
It'll overwrite all the files correctly, and then XYPlorer just exits.

ALSO: If I hit Cancel on the copy dialog asking me what Action I want to take, XYPlorer ALSO exits without having copied a single file.
If I hit Cancel on the merge dialog, XY will SOMETIMES exit.

When I say "XY exits" I mean this:
I can see in the status line of XY that it has the little blue i icon and says "updating tags..."; that'll be on the screen for about a second, and then exit.
When XY exits in this way, it does not save its configuration, so I suspect it's a crash of sorts.

I have narrowed down the scope of this, and it's super weird:
The source in C:\den\config has about 140 files in about 50 folders/subfolders.
I have found out that it's one of those folders that's the root of the problem.

Now, when I copy JUST that folder into the destination, XY dies as described above.
However, when I go into that folder, there are two files (VS project files). If I copy each file separately, or both files together, directly into the target, overwriting them in the destination, XY is fine.
It only crashes when I copy that folder and do folder merge.. again, even if I cancel the merge (SOMETIMES) or overwrite.

Things I observed:
Note how I said that it SOMETIMES crashes when I cancel the Merge.
Sometimes, when I cancel Merge, it does not update tags, or at least I don't see that in the status line. In that case, XY does not exit.

Every time I see "updating tags.." XY will die. I don't know if it finishes updating tags or not.
I am using Labels to quickly see important folders so I label them with a color label.

Here's what I think may be a big hint:
The destination folder has a Red label.
The source folder of the same name does not have a label.
After the files get overwritten and XY exits, when I restart XY, the destination folder still has its Red label, even though that should have been overwritten to not have a label anymore.

I've tried to duplicate this issue with other folders in this structure, the source not having a label but the destination having one. Doesn't cause any problems, the destination loses its label after Overwrite.
It is only on that one folder that it doesn't work that way.


Things I've tried that FIXED the issue:
- The issue is gone with a fresh config
- When I disable "Copy tags on copy operations", the issue is gone

Things I've tried that did not fix the issue (while using my regular config):
- Not using custom copy
- Not using background processing
- Not using custom copy AND not using background processing
- Copying by selecting source with mouse, dragging them to the target folder while holding CTRL (to copy), instead of using the keyboard
- Disabled "Auto-Refresh tags". It won't display "updating tags..." any more, but the little blue i (information) icon, and then crash even faster
- Did a database check on the tags via Options, and had it remove orphans

Things I've tried to narrow the scope:
- Copying the same source file set to a different directory does NOT crash, whether that directory was empty or the files were already there and I overwrote them
- Making a copy of C:\Repo, then copying the files into that new folder, also will NOT crash XY


Given this information, is there anything else you want me to try to find the root cause?

I don't know what'll happen when "Updating tags..." happens next. How do I trigger that?