crash while previewing changes

Posts: 3 · redtech116 25 May 2011, 23:40

v. 3.17
win 7 pro x64
when i set up to mirror 2 different folders to a mapped network drive, it does
the compare (80,000+ files)
when i scroll down using the scroll bar, I get to about the mid 400's files
windows kicks out a message saying the program has crashed.
in the event viewer it say event ID: 1000

any ideas.

(when i don't scroll the preview it mirrors the file fine)

Posts: 7170 · Zenju 26 May 2011, 00:14

Can you give me more details, like what type of mapped network drive are you
using (some cloud provider?) and provide steps how I can reproduce this
problem?

Is there a "LastError.txt" file in the directory containing "lastrun.ffs_gui"
and "globalsettings.xml"?

Posts: 7170 · Zenju 26 May 2011, 00:15

Additionally: Maybe this crash is not arbitrary, but happens on a particular
file? If so, is there something strange with its metadata, file modification
date or its icon?

Posts: 3 · alpalp 27 May 2011, 12:09

It happened to me, too.
Win7 64bit
With 3.16 fine. After migration to 3.17 crash.
System crashes when I compare a local folder to a network folder with nearly
100.000 files.
Network folder is on a video player/network driver appliance with samba
running on it.

Posts: 7170 · Zenju 27 May 2011, 23:56

Can you answer all or some of the questions above? In order to diagnose the
problem I need more information.

Posts: 3 · alpalp 28 May 2011, 06:45

I confirm the crash is not occasional.
I could not find any of the files "LastError.txt" "lastrun.ffs_gui" and
"globalsettings.xml" with Win 7 search

Posts: 7170 · Zenju 28 May 2011, 12:18

> I could not find any of the files with Win 7 search
Can you directly look in %appdata%\FreeFileSync if you are using the local
installation and "<install dir>" if you use the portal installation?

>System crashe ... samba running on it.
Just tested SAMBA but couldn't find an issue about it. There was however a
problem when setting the input path, which I've fixed. At which point exactly
do you see the crash?

Posts: 3 · alpalp 29 May 2011, 16:01

OK, I found the two files in "lastrun.ffs_gui" and "globalsettings.xml" in
"lastrun.ffs_gui" and "globalsettings.xml".

Probably, my problem was in some corrupted files. I confronted the two
directories with Freecommander and I noticed a strange result, some like blank
rows (but it did not crash). So, I manually overwrote part of my archive
(mp3s) and the problem disappeared: no more crashes with Freefilesync 3.17.

Anyway, the crash happened during the confronting phase. I could not find any
"LastError.txt" files, probably because your program polishes that file after
a positively ended run.

Sorry if I made you waste some time.
Great piece of software.

Posts: 7170 · Zenju 29 May 2011, 16:32

> probably because your program polishes that file after a positively ended
run.
It's not that it deletes this file, but it's not created on every crash. Only
if the crash is caused by an uncaught exception.

> I manually overwrote part of my archive (mp3s)
FreeFileSync should never crash no matter how messed up the input data. If you
can find a way to find out what kind of files or invalid data caused this, I
would like to know.

Posts: 3 · redtech116 31 May 2011, 20:55

could not find an lasterror.txt file
only thing i could find was the windows event view item

Faulting application name: FreeFileSync_x64.exe, version: 3.17.0.0, time
stamp: 0x4dd68d35
Faulting module name: FreeFileSync_x64.exe, version: 3.17.0.0, time stamp:
0x4dd68d35
Exception code: 0x40000015
Fault offset: 0x000000000025663d
Faulting process id: 0xd2c
Faulting application start time: 0x01cc1fd15e5f2e40
Faulting application path: C:\Program
Files\FreeFileSync\Bin\FreeFileSync_x64.exe
Faulting module path: C:\Program Files\FreeFileSync\Bin\FreeFileSync_x64.exe
Report Id: b6a8a991-8bc4-11e0-ab88-0090f54ff80a

Posts: 7170 · Zenju 31 May 2011, 21:04

Okay, these crash dumps don't really help.

Can you identify a single file which makes the app crash when displayed? Or is
it random?

Posts: 3 · redtech116 31 May 2011, 21:06

here is a lasterror.txt
Conversion error: SYSTEMTIME -> local SYSTEMTIME: (UTC <strike>: 910692730085
UTC System time: 30828 9 14 2 48 5)

Windows Error Code 87: The parameter is incorrect. </strike>

Posts: 7170 · Zenju 1 Jun 2011, 15:36

> 30828 9 14 2 48 5
This means you have a file with modification time
year: 30828
month: 9
date: 14
hour:2
minute: 48
second: 5

FFS crashing is a clear proof Windows is not year-30828 ready :D

Result:
We have two bugs:
1. one of your file's has a corrupted modification time
2. FFS shouldn't crash on invalid file dates

2 -> fixed for next release. I was throwing an exception if number formatting
fails. No idea what I was thinking!

Here's a link to the 32-bit binary for testing:
[404, Invalid URL: http://www.file-upload.net/download-3475210/FreeFileSync_Win32.rar.html]