Program crashes every time I run a scan. It scans everything, says "Generating file list", then once it gets to "Calculating sync directions", it crashes. I'm on linux, so a terminal window pops up that says:
Error running "/opt/FreeFileSync/Bin/FreeFileSync_x86_64".
Killed by signal SIGABRT
<Press a key>
If I run the program through a terminal window as sudo, I get these errors before the crash:
(FreeFileSync_x86_64:12961): Gtk-CRITICAL **: 10:35:34.386: IA__gtk_widget_set_sensitive: assertion 'GTK_IS_WIDGET (widget)' failed
(FreeFileSync_x86_64:12961): Gtk-CRITICAL **: 10:35:34.387: IA__gtk_widget_set_sensitive: assertion 'GTK_IS_WIDGET (widget)' failed
(FreeFileSync_x86_64:12961): Gtk-CRITICAL **: 10:35:34.387: IA__gtk_widget_set_sensitive: assertion 'GTK_IS_WIDGET (widget)' failed
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
Error running "/opt/FreeFileSync/Bin/FreeFileSync_x86_64".
Killed by signal SIGABRT
Anyone know what this could be? I've tried rebooting, uninstalling/reinstalling FFS, downgrading to an earlier update, and deleting every .ffs_db file on my drives. I've also tried getting a memory dump with the instructions from the FAQ, but nothing is being written. I assume it's an issue with my system, but I'm not sure what it could be. std::bad_alloc looks like a RAM issue, but that seems weird, It's only using 15-20% of my RAM, and there isn't any spike before the crash or anything. It was working fine just yesterday, though I had to stop a sync in the middle at one point, so maybe something screwed up when that happened?
Killed by signal SIGABRT
- Posts: 1
- Joined: 29 Oct 2025