I have a FFS installed on a Windows Server 2012 NAS. FFS was working perfectly for almost a year when it stopped working. NAS does not get updated, it is a file store for a remote site conected to the main office. FFS would sync network files from the main server across the WAN to itself. When you start FFS, it opens, accessible up until the SYNC is activated. 3-5 Seconds after choosing to sync, AppCrash message occurs and log is placed on desktop. I've updated to latest revision as well, same error occurs.
TAI - Steve
AppCrash Error...
- Posts: 4
- Joined: 30 Jul 2015
- Posts: 4
- Joined: 30 Jul 2015
Log...
[Attachment was removed! File name: FreeFileSync_x64.exe CrashDump 2015-07-21 171348.dmp (2455019 bytes)]
[Attachment was removed! File name: FreeFileSync_x64.exe CrashDump 2015-07-21 171348.dmp (2455019 bytes)]
-
- Site Admin
- Posts: 7323
- Joined: 9 Dec 2007
Looks like a crash while scanning an extremely deep hierarchy of folders like "recyclebin.ffs_tmp\ ...."
This is caused by some item within these folders that can be moved but not recycled. In combination with FFS's behavior of first moving to be deleted items into a temporary folder this creates the problem of increasing the folder depth of these temp folders for each failed sync - so long until traversing these folders leads to a stack overflow.
Meanwhile FFS's behavior has been changed for the next release, so that the folder depth is stable during errors and therefore this situation won't occur in the future, however the clean-up of these folders must be done manually once:
[404, Invalid URL: https://freefilesync.org/FreeFileSync_7.3_beta_Windows_Setup.exe]
This is caused by some item within these folders that can be moved but not recycled. In combination with FFS's behavior of first moving to be deleted items into a temporary folder this creates the problem of increasing the folder depth of these temp folders for each failed sync - so long until traversing these folders leads to a stack overflow.
Meanwhile FFS's behavior has been changed for the next release, so that the folder depth is stable during errors and therefore this situation won't occur in the future, however the clean-up of these folders must be done manually once:
[404, Invalid URL: https://freefilesync.org/FreeFileSync_7.3_beta_Windows_Setup.exe]
- Posts: 4
- Joined: 30 Jul 2015
I've cleaned out recycle bin's on both side. I also cleaned out temp files then I updated to posted version, it is still happening. Please expand on "clean-up of these folders" from previous post, I'mprobably missing something - thanks!
[Attachment was removed! File name: FreeFileSync_x64.exe CrashDump 2015-08-05 144537.dmp (2292541 bytes)]
[Attachment was removed! File name: FreeFileSync_x64.exe CrashDump 2015-08-05 144537.dmp (2292541 bytes)]
-
- Site Admin
- Posts: 7323
- Joined: 9 Dec 2007
>I've cleaned out recycle bin's on
Did you delete the "recyclebin.ffs_tmp" directories? I'm not talking about Windows recycle bin.
Then retry with the current FFS 7.3 from https://freefilesync.org/
Did you delete the "recyclebin.ffs_tmp" directories? I'm not talking about Windows recycle bin.
Then retry with the current FFS 7.3 from https://freefilesync.org/
- Posts: 4
- Joined: 30 Jul 2015
Cleaning out the "legion" of "recyclebin.ffs_tmp directories did it. I had to use 7zip File Manager with SHIFT+DEL to knock out all of those subfolders. A sync is now running, I'll post back if it appears again. Thank you sir!
