XYplorer Beta Club

Lately when I've been moving files from one network location to another network location, I'm having problems with XYplorer hanging/freezing until the move is complete. Both network locations are on the same PC on the network, on two different drives. In other words, I'm using XYpolorer on PC 1, and I'm moving files from PC 2 drive D to PC 2 drive E (or vice versa). Copy/pastes are fine. Cut/pastes (move) are the only issue.

If I don't use Custom Copy (just Windows copy) - no issues. But I normally use Custom Copy (XYplorer).

Note, I'm seeing some slow file transfer speeds - slower than if I open the same two network folders in Windows Explorer and move from one to the other there. I have not done any troubleshooting on the transfer speeds yet, but regardless, I would expect that even on a slow file transfer, XYPlorer/XYCopy should just chug along moving files without hanging or freezing in any way.

Background Processing is enabled and Apply To is checked for all operations. However I also tested with Background Processing disabled and it made no difference.

Using Custom Copy (XYplorer) with "No progress dialog on intra-volume moves" checked (so I do NOT have a progress dialog - this is how I normally have it set so this is how it was when I began to notice the behavior) - XYplorer hangs ("Not Responding") until the move is complete. Also it doesn't appear to do it as a background job - XYcopy.exe does not appear in the process list, afterward the status bar says "Custom move completed in...", and the move does NOT appear in the Background Jobs log.

Using Custom Copy (XYplorer) with "No progress dialog on intra-volume moves" UNchecked (so I DO have a progress dialog) - XYplorer does NOT hang - but the dialog box itself does hang ("Not Responding") until the move is complete. XYcopy.exe appears in the process list (and shows "not responding" there). Also the progress dialog does refer to the job as "Background Job" and afterward the status bar says "all background jobs completed" and the move appears in the Background Jobs log.


I've also played with the Auto-Refresh settings - I normally have Auto-Refresh enabled, including for network locations, and "Refresh during file operations" NOT enabled. But I played around with turning "include network locations" off and turning off auto-refresh completely, but it made no difference.

Also tried disabling "Preserve permissons on move operation" and "File operation progress dialog modeless" (normally they are both enabled), made no difference.

Also tried disabling "Log actions and enable undo/redo" (normally enabled), made no difference.

Under Network settings, I have:
- Fast network enumeration UNchecked
- Assume that servers are available checked
- Pre-check availability of servers UNchecked
- Cache network servers checked

(Had to play with these not too long ago because I was seeing really slow startup time in XYplorer. Can't remember what they were before, but this arrangement really sped it up. But I played around with them a bit now and none seemed to make any difference on this issue.)

I normally use Ctrl+X and Ctrl+V, but I also experimented with using the toolbard cut/pate buttons instead as well as right-click drag/drop; made no difference.

If a file transfer happens fast enough, no freeze will happen. Hard to say what exactly the "cutoff point" might be, I just know that if I transfer small files, there's no issue, but moving large video files (the ones that I was moving when I started noticing this - and that I've been testing with - are at least 500mb and up) causes it to choke. It might be that the same problem would theoretically appear even on same-drive or local-PC transfers, but perhaps those simply transfer fast enough that it doesn't appear. Also disabling file verification (I normally have it on MD5) helps for the same reason - it makes it more likely that a file might finish transferring before XYplorer hangs - but it doesn't resolve it - many files still take long enough that it hangs. We're talking a few seconds - I'd say the hang kicks in if a transfer takes more than a few seconds.

Are you saying this is a new problem with the recent version that had not been there before?

Sorry, I didn't have notifications on so I didn't see this until now!

Well, I only noticed it when I was on 20.20.0100 - but I can't be certain I wouldn't have observed it before if I had happened to be moving those same large files around those same drives before. It could just be that I only observed it now because now is when I happened to do this. I really can't recall the last time I would have been moving similar files across the network drives like that -- certainly at various times over the years - but I'm really not sure when the last time was that I would have been doing something similar. Sorry that's not very helpful.

admin wrote: ↑15 Jul 2019 13:31 Are you saying this is a new problem with the recent version that had not been there before?

I have the exact same issue only noticed this in the last few days. started file transfer using XYplorer files seemed to not be moving after several minutes. Stopped file transfer using XYplorer used windows explorer process took less than 2 min.

I cannot see how this can happen. If Background Processing is enabled the whole copying is handled by a different process and cannot possibly affect XYplorer. Mysterious.

Thinking back on what I typed out before - *is* it actually using Background Processing? How would I verify this? The reason I ask is because of this:

Using Custom Copy (XYplorer) with "No progress dialog on intra-volume moves" checked (so I do NOT have a progress dialog - this is how I normally have it set so this is how it was when I began to notice the behavior) - XYplorer hangs ("Not Responding") until the move is complete. Also it doesn't appear to do it as a background job - XYcopy.exe does not appear in the process list, afterward the status bar says "Custom move completed in...", [instead of "all background jobs completed"] and the move does NOT appear in the Background Jobs log.

So I get the following results in these scenarios (all with Custom Copy XYplorer in use):

- Background Processing disabled - XYplorer hangs on the aforementioned types of file moves
- Background Processing enabled with NO progress dialog - XYplorer hangs on these types of file moves - but as far as I can tell, isn't actually using Background Processing.
- Background Processing enabled WITH progress dialog - XYplorer does NOT hang on these moves - DOES appear to use Background Processing - XYcopy.exe DOES hang on its own but that is at least less annoying because it doesn't stop me doing other things in XYplorer

So even leaving aside the fact that XYcopy.exe also hangs on these types of file moves when it is doing Background Processing, if XYplorer only hangs when it's NOT using Background Processing AND it's not actually using Background Processing for some reason when the progress dialog is disabled, then that would explain why I see it hanging in both of the first two scenarios. (No idea why it's hanging in the first place, though.)

To find out why it is not using background processing I would need to know source and target path of the operation.

For anyone having the same problem, please check "move intra volume" in settings - file operation - background processing - apply to.

Problem is that even if it is intra volume move, like from \\192.168.1.50\test\1 to \\192.168.1.50\test\2, since it is a network drive (in my case a SMB drive on local network) the operation is not instantaneous. I wonder if there should be a separate option for network drives.