FreeFileSync Forum

No need to wait; here's the new beta version for testing:
[404, Invalid URL: https://freefilesync.org/FreeFileSync_6.15_beta_Windows_Setup.exe]
Using the beta version I got a message like shown in the attachment for all directories that contained files or directories having a German Umlaut in it's ...

So the root cause of the invalid item with empty name is a problem in the Windows network layer that has trouble to translate the Linux name. I'm not sure if the german ß is really the (only) problem: a dirname ending with newline is certainly also a recipe for problems. Anyway, the solution in ...

Thanks Gregor, the new dump file helped a lot:
It turns out the crash is caused by an out-of-stack space issue due to an endless directory recursion. This also explains why the automatic mini dump creation facility failed.
The reason for this endless recursion is that FFS at one point finds a ...

@Gregor, @Singgih:
Thanks for the latest dump file and windows crash information. I'm now able to identify the code location where the crash is happening, but the call stack is corrupted. Therefore it's hard to analyze further, but I could find out that the crash occured in the routine that created ...

I only see "FreeFileSync_full_dump.zip" in your cloud dir. Can you send me the link to the new "FreeFileSync_full_dump_3_4.zip"?Zenju

Sorry, I forgot to share the file. Now you should see it.

I add FreeFileSync_full_dump_3_4 to my cloud directory.

And here is the information of the windows crash dialog:

Problemsignatur:
Problemereignisname: APPCRASH
Anwendungsname: FreeFileSync_Win32.exe
Anwendungsversion: 6.13.0.0
Anwendungszeitstempel: 54d7b975
Fehlermodulname: ntdll.dll ...

I created crash dump files by Process Explorer as described. The compressed file has 46 MB. I'm uploading it to my cloud and send you the link if the upload is complete.

Oops, I found a file (in folder Desktop), but unfortunately the size is 0.

I attached the sreenshot, but i cannot find a crash dump file (searched the whole drive for files having a current timestamp).

Do you have a hint where to search for it somewhere else?

I detected 2 files sync.ffs_lock having a current timestamp in the root directory of the synced directories. These and the sync.ffs_db files I attached to this post.

I don't know about the content of the files. Thus I send you a password by mail.

[Attachment was removed! File name: FFS_6_13_debug ...

FFS crashes with this debug version, too.

Thanks.

I'm away on business and will try in a few days.

Gregor

Since about 2 - 3 weeks FreeFileSync crashes and Windows shows the following message:

--------------------
Problemsignatur:
Problemereignisname: APPCRASH
Anwendungsname: FreeFileSync_Win32.exe
Anwendungsversion: 6.13.0.0
Anwendungszeitstempel: 00000000
Fehlermodulname: ntdll.dll ...