It appears the the program takes three minutes or more to abort a batch sync
when I try to manually abort it. I wonder why that is. I would open the
program, click abort, and I would sit there watching it for three minutes
until it will finally abort. Sometimes, a Windows dialog box would come up and
say the program is not responding, I can either a) wait for the program to
respond, or b) straight kill the program. I always opt to wait for the program
to respond because I like having the program write to the log file when it
aborts. However, the wait is a huge pain. Is there anyway to improve this?
Slow to Abort Batch Sync
- Posts: 5
- Joined: 15 Sep 2011
-
- Site Admin
- Posts: 7307
- Joined: 9 Dec 2007
An application hangs if it is not processing GUI messages. FFS does this after
each element (file/dir/symlink) which is processed and also during file copy,
roughly about every 64 kb. So the culprit must be some system call does does
not respond for three minutes. Can you describe what FFS was doing while the
hang occurs and your setup? Examples for system calls which may show similiar
behavior are VSS initalization, or USB cache flushes.
each element (file/dir/symlink) which is processed and also during file copy,
roughly about every 64 kb. So the culprit must be some system call does does
not respond for three minutes. Can you describe what FFS was doing while the
hang occurs and your setup? Examples for system calls which may show similiar
behavior are VSS initalization, or USB cache flushes.
