Hi
I'm using FreeFileSync 6.14 on Windows 7 64bit and sync to a folder I've mapped as a network drive which is located on Mac OS X 10.9.5. To complicate things even more: This folder I sync to is located on an external USB drive connected to the Mac.
This used to work just fine but for a few weeks I noticed it never completed. I have a scheduled daily sync which seems to stop in the middle of comparing the folders. Running the .ffs_batch manually from inside the FreeFileSync app also makes the program crash. There's always an empty (0 bytes) crash dump stored on the desktop, which obviously doesn't help much.
I've seen that you're very helpful for other users having issues, could you help me out as well?
Thanks!
Pieter
Crash when attempting a sync between win & mac
- Posts: 4
- Joined: 28 Jun 2005
-
- Site Admin
- Posts: 7282
- Joined: 9 Dec 2007
Sure, here are the steps:
Download the tool Process Explorer (https://technet.microsoft.com/de-de/sysinternals/bb896653.aspx), then reproduce the crash with FFS, start Process Explorer, right-click on the FreeFileSync_x64.exe, select "Create Dump" and then "full dump". Next, compress this file and send it to me via email (see FFS's about dialog for my email). This should help me find out what FFS was doing during the crash.
Download the tool Process Explorer (https://technet.microsoft.com/de-de/sysinternals/bb896653.aspx), then reproduce the crash with FFS, start Process Explorer, right-click on the FreeFileSync_x64.exe, select "Create Dump" and then "full dump". Next, compress this file and send it to me via email (see FFS's about dialog for my email). This should help me find out what FFS was doing during the crash.
- Posts: 4
- Joined: 28 Jun 2005
Thanks for the quick response!
Unless I'm doing something wrong, that method isn't working. When FFS crashes the process itself obviously dissapears so there's no way for me to create a dump after the crash happened. I also didn't find any way to permanently 'attach' process explorer to FFS, so it looks like I'm stuck.
(If I start process explorer after the FFS crash there's no sight of the process, if I start process explorer before I can see the process go away immediately after the crash. Both these behaviors seem pretty normal to me so I'm a bit confused how I should be able to get a dump out of the process this way.)
Unless I'm doing something wrong, that method isn't working. When FFS crashes the process itself obviously dissapears so there's no way for me to create a dump after the crash happened. I also didn't find any way to permanently 'attach' process explorer to FFS, so it looks like I'm stuck.
(If I start process explorer after the FFS crash there's no sight of the process, if I start process explorer before I can see the process go away immediately after the crash. Both these behaviors seem pretty normal to me so I'm a bit confused how I should be able to get a dump out of the process this way.)
-
- Site Admin
- Posts: 7282
- Joined: 9 Dec 2007
When a process crashes, you should always see the Windows crash dialog; otherwise the process hasn't crashed but exitted normally.
Anyway you can also test the new FFS 6.15 and see how it works.
Anyway you can also test the new FFS 6.15 and see how it works.
- Posts: 4
- Joined: 28 Jun 2005
I think I disabled the standard app crash dialog in my setup, which explains why that happened. (It's the Windows Error Reporting Service.)
The newer 6.15 version doesn't crash anymore during comparision, and I'm doing a new sync right now. So it looks like the issue I had is now solved.
Thanks a lot!
The newer 6.15 version doesn't crash anymore during comparision, and I'm doing a new sync right now. So it looks like the issue I had is now solved.
Thanks a lot!
-
- Site Admin
- Posts: 7282
- Joined: 9 Dec 2007
It would still be interesting to analyze what went wrong with 6.14. Although the symptoms are gone in 6.15, the underlying cause might very well still exist.
- Posts: 4
- Joined: 28 Jun 2005
I agree, I've mailed you a link to the dump I was now able to create using version 6.14.
-
- Site Admin
- Posts: 7282
- Joined: 9 Dec 2007
The crash is a stack overflow caused by encountering a folder with an empty name (= data corruption). => same issue as discussed here:
viewtopic.php?t=364
The problem occurred when traversing the following folder:
Z:\WPRDBELMCGLVW backup\Pieter_VN_Workdir_mirror\tools\sonar-3.6.3\war\sonar-server\images
The new FFS 6.15 handles this case and does not crash anymore. It outputs the diagnostic message "Data corruption: Found item without name." should this problem occur. Since you didn't see this message when testing 6.15, the underlying cause for this corruption must have been temporary.
viewtopic.php?t=364
The problem occurred when traversing the following folder:
Z:\WPRDBELMCGLVW backup\Pieter_VN_Workdir_mirror\tools\sonar-3.6.3\war\sonar-server\images
The new FFS 6.15 handles this case and does not crash anymore. It outputs the diagnostic message "Data corruption: Found item without name." should this problem occur. Since you didn't see this message when testing 6.15, the underlying cause for this corruption must have been temporary.
