Page 5 of 5
Re: XYCopy refuses to exit. Multiple running copies. Can't be killed.
Posted: 28 Nov 2021 20:12
by admin
Re: XYCopy refuses to exit. Multiple running copies. Can't be killed.
Posted: 29 Nov 2021 09:06
by admin
Thanks, got it.
But again, could not repro it. :\
Re: XYCopy refuses to exit. Multiple running copies. Can't be killed.
Posted: 29 Nov 2021 20:59
by Jeeves
admin wrote: ↑29 Nov 2021 09:06
Thanks, got it.
But again, could not repro it. :\
As noted previously; I'm happy to do any steps or run nay tools that might help.
As for the delete bug; I have run into it on both machines in the last 6 hours, somehow.
XYCopy v2.10.0181
XYPlorer v22.50.0107
Jobs 8 & 9 were the same files. I don't know why 9 finished, but 8 is "In Progress".
Jobs 10 & 11 were queued together under a minute after the above.
Jobs 12 & 13 were pending, when I started #12 manually, #13 followed and ran as well.
Jobs 14 & 15 I copied & pasted a file (twice) to confirm. If I start either #14 or #15, the other will run as well.
Re: XYCopy refuses to exit. Multiple running copies. Can't be killed.
Posted: 30 Nov 2021 00:09
by Jeeves
Jeeves wrote: ↑29 Nov 2021 20:59
admin wrote: ↑29 Nov 2021 09:06
Thanks, got it.
But again, could not repro it. :\
As noted previously; I'm happy to do any steps or run nay tools that might help.
As for the delete bug; I have run into it on both machines in the last 6 hours, somehow.
XYCopy v2.10.0181
XYPlorer v22.50.0107
Jobs 8 & 9 were the same files. I don't know why 9 finished, but 8 is "In Progress".
Jobs 10 & 11 were queued together under a minute after the above.
Jobs 12 & 13 were pending, when I started #12 manually, #13 followed and ran as well.
Jobs 14 & 15 I copied & pasted a file (twice) to confirm. If I start either #14 or #15, the other will run as well.
I minimized everything on both machines. The delete dialogs were behind everything.
I'm not sure if anything needs to be done as there is certainly a factor of operator error in this.
Re: XYCopy refuses to exit. Multiple running copies. Can't be killed.
Posted: 30 Nov 2021 06:48
by admin
Each instance of XYcopy (the background copy handler) should be visible as an icon in your task bar. If you click on it it will jump to the foreground and you should see the confirmation prompts.
But I'd generally recommend to exclude Delete operations from the background operations here: Configuration | File Operations | File Operations | Background Processing | Apply to...
Re: XYCopy refuses to exit. Multiple running copies. Can't be killed.
Posted: 15 Dec 2021 04:12
by Jeeves
admin wrote: ↑30 Nov 2021 06:48
Each instance of XYcopy (the background copy handler) should be visible as an icon in your task bar. If you click on it it will jump to the foreground and you should see the confirmation prompts.
But I'd generally recommend to exclude Delete operations from the background operations here:
Configuration | File Operations | File Operations | Background Processing | Apply to...
I will look into the above, thank you.
However I came to update regarding the XYCopy .. quirk?
I went to reboot today and found four copies of XYCopy (attachment1). Investigating them with Process Hacker shows that they have no active windows (attachment2). There are also no background tasks pending or in progress in XYplorer. Closing XYplorer and the XYcopy instances remain (attachment3).
If I execute killxycopy; the copies of XYcopy terminate.
Re: XYCopy refuses to exit. Multiple running copies. Can't be killed.
Posted: 15 Dec 2021 08:41
by admin
Jeeves wrote: ↑15 Dec 2021 04:12
admin wrote: ↑30 Nov 2021 06:48
Each instance of XYcopy (the background copy handler) should be visible as an icon in your task bar. If you click on it it will jump to the foreground and you should see the confirmation prompts.
But I'd generally recommend to exclude Delete operations from the background operations here:
Configuration | File Operations | File Operations | Background Processing | Apply to...
I will look into the above, thank you.
However I came to update regarding the XYCopy .. quirk?
...
The first will fix the latter...
