FFS 5.3 hangs with batch file

[webserver81]

Hi all,

I'm new in this forum and I'm using FFS since last week to sync my files on my
local c: drive with our read only network drive. I run FFS in a batch and I
need to wait till the program has finished the sync job.

START /wait "C:\Program Files\FreeFileSync\FreeFileSync.exe"
"C:\SyncJob.ffs_batch"

Now I have the problem that sometimes (1 of 5 trials) FFS does not end the
process. The sync job is done (I can see all files were updated) but the
process is still running (FreeFileSync.exe and FreeFileSync_Win32.exe). When I
start the batch again, I can see the FreeFileSync.exe twice in Windows Task
Manager. My batch settings are:

On Error: Ignore

Anybody encountered same problem?

Thanks!
Christian

[Zenju]

The prime candidates for making an application hang on exit are modal dialogs.
With "error: ignore" and not showing the results dialog (I assume you
unchecked this also), you have avoided the main culprits.
If the problem is reproducible and you want me to analyze it (which means you
will have to provide mit with much more details) open a new bug tracker item.

[urdailo]

I am seeing this under Version 5.2.
I have it running as a task on a Windows 2008R2 box in Task Scheduler.

Step 1) FreeFileSync.exe SyncJob.ffs_batch
Step 2) Zip Log file and clean directory
Step 3) Email the Zipped Log

All tasks would completed with a previous verison 3.14.
With 5.2, I see from the FreeFileSync log that the task completes:
Info: Synchronization completed successfully!
Stop (Total time: xx:xx:xx)

Here is another thing, the sync used to take an hour, now it takes 8 hours
before it start performing the file operations.

[Zenju]

Please open a new tracker item if you think you found a bug (after reading the
help on scheduling)

[urdailo]

Resolved the problem Task Scheduler jobs, I made sure the Status feedback Show
progress dialog is unchecked. and Error handling is set to Ignore errors.

As for the long sync time, perhaps it is just that there are so many files to
compare, I have watched a manual invokation of the batch file, and that seems
to go ok.

Thanks for a great tool.