Mac OS X version 6.10 not terminating FFS and RTS processes on exit

Posts: 73 · htismaqe 8 Oct 2014, 18:46

I noticed this on the previous version when I upgraded to the latest version and I'm still seeing it.

I exited out of both FFS and RTS before upgrading to the latest version and when I tried to copy the new apps, I was given a warning that the apps were in use and could not be updated.

If I go to File | Quit in FFS or if I click on the Status Menu icon for RTS and select "Quit", the programs appear to close correctly.

However, if I then look at running processes, both FFS and RTS are still running. The only way to terminate them is to kill the process.

Posts: 7281 · Zenju 12 Oct 2014, 14:05

This is a side-effect due to the FFS launcher mapping the OS X MDI concept to the FreeFileSync app. I'll see to implement a fix that solves this limitation.

Until then the workaround is to restart OS X or to quit the FreeFileSync process in the OS X Activity Monitor.

Posts: 73 · htismaqe 14 Oct 2014, 20:52

OK cool. Thanks for the response.

Posts: 7281 · Zenju 16 Oct 2014, 20:47

I've updated the FreeFileSync launcher to automatically exit once all of its child processes (= FreeFileSync windows) have ended. This should fix the issue discussed above.

Here's the new version for testing. Let me know if there are still problems:

[404, Invalid URL: http://freefilesync.sourceforge.net/FreeFileSync_6.11_beta_Mac_OS_X_64-bit.zip]

Posts: 73 · htismaqe 16 Oct 2014, 22:16

I will test it tomorrow and let you know. Thanks for all your hard work!

Posts: 1 · storagekid 21 Oct 2014, 10:24

I will test it tomorrow and let you know. Thanks for all your hard work!htismaqe

Thanks, I've been having the same issue and now it works perfectly.

Posts: 73 · htismaqe 22 Oct 2014, 14:47

Sorry for the late response. I had a drive die in my NAS and I made the mistake of installing OS X Yosemite over the weekend.

I have confirmed as of this morning that this problem is fixed in the 6.11 beta.

Thank you for your efforts!