Hi, every time I run Synchronise in FreeFileSync, the 'On Completion' drop down menu defaults to a blank, and if I forget to change it to one of the options, after completing the synchronisation, it crashes (I have Windows 8 64 bit, Freefilesync 6.1). It's only started defaulting to the blank part of the 'On Completion' menu in the past few weeks, I think that before it defaulted to the first option (I can't remember what it was now, something like 'Close synchronise window').
Has anybody else had this problem? I uninstalled and reinstalled it, and it's still happening.
To the developer(s), I LOVE Freefilesync. It's fantastic, easy to use, shows me exactly what it's copying over and what it's deleting before I say continue, it tells me if the target directory is significantly different to the source directory before doing anything serious, a fantastic program.
'On completion' drop down empty, causes crash
- Posts: 2
- Joined: 15 Sep 2012
-
- Site Admin
- Posts: 7281
- Joined: 9 Dec 2007
Are you able to reproduce the crash? In general there are two ways how to fix such a problem:
1. you find some conditions that allow me to reproduce the problem on my machine
2. I send you a debug version of FreeFileSync that can be used to create crash dump files for analysis
1. you find some conditions that allow me to reproduce the problem on my machine
2. I send you a debug version of FreeFileSync that can be used to create crash dump files for analysis
- Posts: 2
- Joined: 15 Sep 2012
Hi Zenju, it happens every time I run Freefilesync. I have five different backups, 6TB of data on three drives, every time I click the 'Synchronise' button, then 'Start', the 'On completion' drop down box is empty, and if I only have a small amount of data to sync over, it finishes and thus crashes before I can change the drop down box to 'Close progress dialog'.
Presumably it should never have nothing in the drop down box? I know it only started a few weeks ago.
I installed a demo of Sonar X3 (music software) and that installed some Microsoft Visual C++ Redistributable libraries, could it have anything to do with those? I had problems with the demo of Sonar X3, some parts of the interface wouldn't respond to mouse clicks, even though they responded to keyboard shortcuts. I was wondering if maybe I have too many C++ libraries installed, I have 2005, (five entries in 'Add or Remove Programs'), 2008 (four entries), 2010 (two entries), and one of 2013. Should I just have the latest one? Or is this nothing to do with it? (These were all installed by various programs I've installed over the past year or so.)
Or you can send me a debug version, that's fine, I can send you the crash dump files. Thanks for looking into this - still loving Freefilesync!!!
Presumably it should never have nothing in the drop down box? I know it only started a few weeks ago.
I installed a demo of Sonar X3 (music software) and that installed some Microsoft Visual C++ Redistributable libraries, could it have anything to do with those? I had problems with the demo of Sonar X3, some parts of the interface wouldn't respond to mouse clicks, even though they responded to keyboard shortcuts. I was wondering if maybe I have too many C++ libraries installed, I have 2005, (five entries in 'Add or Remove Programs'), 2008 (four entries), 2010 (two entries), and one of 2013. Should I just have the latest one? Or is this nothing to do with it? (These were all installed by various programs I've installed over the past year or so.)
Or you can send me a debug version, that's fine, I can send you the crash dump files. Thanks for looking into this - still loving Freefilesync!!!
-
- Site Admin
- Posts: 7281
- Joined: 9 Dec 2007
> it happens every time
Great! (that is, speaking as a developer) We should be able to trace this bug in no time.
> Presumably it should never have nothing in the drop down box?
An empty box is the default and should not be an issue. But maybe it is somehow the trigger for the crash.
> Visual C++ Redistributable libraries, could it have anything to do with those
I don't think so. FFS is statically linked to its own version of the C++ runtime, so it shouldn't matter what other versions you have installed.
> was wondering if maybe I have too many C++ libraries installed
That's not a problem in general. Each of your applications that depend dynamically on the C++ runtime will pick the right version automatically. There are so many versions of this runtime, it's normal that the number of entries in "Add or Remove Programs" grows large over time.
> send me a debug version, that's fine, I can send you the crash dump files.
Okay let's do this. Copy the files from the following archive into your FFS 6.1 installation sub-directory "bin" overwriting the "FreeFileSync_x64.exe" that's already in there. Then reproduce the crash. If you're lucky FFS will already have placed a "crash.dmp" file in the FFS working directory. If not, then start Sysinternals "Process Explorer", right-click on the "FreeFileSync_x64.exe" and select "Create Dump -> Create Full Dump". Then send this file to me (e.g. via email, see FFS's about dialog).
[404, Invalid URL: http://freefilesync.sourceforge.net/FFS_6.1_debug.zip]
Great! (that is, speaking as a developer) We should be able to trace this bug in no time.
> Presumably it should never have nothing in the drop down box?
An empty box is the default and should not be an issue. But maybe it is somehow the trigger for the crash.
> Visual C++ Redistributable libraries, could it have anything to do with those
I don't think so. FFS is statically linked to its own version of the C++ runtime, so it shouldn't matter what other versions you have installed.
> was wondering if maybe I have too many C++ libraries installed
That's not a problem in general. Each of your applications that depend dynamically on the C++ runtime will pick the right version automatically. There are so many versions of this runtime, it's normal that the number of entries in "Add or Remove Programs" grows large over time.
> send me a debug version, that's fine, I can send you the crash dump files.
Okay let's do this. Copy the files from the following archive into your FFS 6.1 installation sub-directory "bin" overwriting the "FreeFileSync_x64.exe" that's already in there. Then reproduce the crash. If you're lucky FFS will already have placed a "crash.dmp" file in the FFS working directory. If not, then start Sysinternals "Process Explorer", right-click on the "FreeFileSync_x64.exe" and select "Create Dump -> Create Full Dump". Then send this file to me (e.g. via email, see FFS's about dialog).
[404, Invalid URL: http://freefilesync.sourceforge.net/FFS_6.1_debug.zip]
