Internally, Duplicati will ask the library to stop doing whatever it is doing. However, it is not possible to always stop the process, so in some cases it may take a little while before it responds. In some cases, and maybe the SMB library is especially bad here, the stop signal is simply ignored and the processing can hang indefinitely.
With the latest canary release, we have added the option to run in an isolated process. The spawned process then runs the backup. If you click “abort”, this will then kill the process completely so it does not matter if it handles the stop signal. It is still an experimental feature as we might need to tweak some option transfers between the processes.
Note: I have posted this in multiple places, so forgive me if this looks like spam.
An unwanted reply, but keeping with the theme of the original post.
I have used Duplicati for over ten years, I run it on multiple systems (laptops, desktops, servers) and I have never had the “STOP” feature work. Ever.
All I do is kill the process, or log out, or restart the machine, which kills it.
The damn thing just doesn’t work and I don’t recommend that anyone spends any time trying to make it work, there seems to be a low-level issue here and the devs will no doubt get to in once they have stamped out the millions of other bugs holding things up.