FreeFileSync close after Compare in Ubuntu Error: std::bad_alloc

[jfmoura]

I am an old user of FreeFileSync, but for some reason, it is not working today.
After comparing folders, the application unexpectedly closes with both my user and root.
The operating system is Ubuntu 22.04.
I reinstalled version 13.0, but nothing happened.

Using prompt:
> sudo FreeFileSync
Error: std::bad_alloc

> sudo FreeFileSync
Error: std::bad_alloc

My PC specs:
Description: Ubuntu 22.04.3 LTS
Mem: 16Gi
Swap: 7,2Gi
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 39 bits physical, 48 bits virtual
CPU(s): 8
Vendor ID: GenuineIntel
Model name: Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz

Thanks in advance for every help; my backups are waiting for your knowledge :-D

[jfmoura]

> FreeFileSync
Error: std::bad_alloc

[therube]

So FFS has remained constant (& has worked as expected in the past).

How about 22.04.3 LTS?
Has that changed since your last successful FFS?

Wonder if "Address sizes: 39 bits physical, 48 bits virtual" has any bearing, & something (that needs to) is not being taken into consideration, resulting in an "overflow" ?
They use an instruction set which allows a full 64-bit address space, but current CPUs just only use the lower 48 bits.

[jfmoura]

This issue started, and I upgraded to FFS version 13.0, but the issue continued.

Ubuntu 22.04.3 LTS is the operating system that I'm using since it release, I haven't made recent updates, but it indicates that it's up to date.

"I wonder if 'Address sizes: 39 bits physical, 48 bits virtual' has any significance, and something (that should) is not being taken into account, resulting in an 'overflow'?"

How can I check this point?
What else can I provide that would be helpful?"

[Zenju]

Could this be a simple case of "not enough free memory available"?

[jfmoura]

Noup.
I made a test with /etc folder and I ran:

top - 22:39:03 up 6:08, 2 users, load average: 0,66, 1,21, 1,42
Tasks: 374 total, 1 running, 368 sleeping, 4 stopped, 1 zombie
%Cpu(s): 4,1 us, 1,4 sy, 0,0 ni, 94,3 id, 0,2 wa, 0,0 hi, 0,0 si, 0,0 st
MiB Mem : 15863,5 total, 4673,8 free, 5084,0 used, 6105,7 buff/cache
MiB Swap: 7419,0 total, 6561,0 free, 858,0 used. 9589,5 avail Mem

4.5 gigabytes free, which is more than enough to handle this folder content (18MB).

[jfmoura]

Hi everyone!
I solved my issue by removing the file:
~/.config/FreeFileSync/
I hope this will help others with the same problem.

Thank you for your help.
🤔

[Zenju]

noooo... that destroyed the test case. I was just about to send troubleshooting instructions. :(

[therube]

Is ~/.config/FreeFileSync/ like %appdata% on Windows?

And if so, what it would have been some setting in GlobalSettings.xml that you're thinking caused the issue?

[therube]

unexpectedly closes with both my user and root

Would root have it's own /.config/FreeFileSync/ ?
If so, there's still hope ;-).

[Zenju]

unexpectedly closes with both my user and root

Would root have it's own /.config/FreeFileSync/ ?
If so, there's still hope ;-).

No, it's the same path in both cases. FFS considers "root" as a request for elevation, not impersonation, in the same way that "run as admin" on Windows only elevates, but does not change persona.

[jfmoura]

Hello Zenju.
I have the same issue again under same conditions.
Excuse me for destroyed the last test case.
Please send me your troubleshooting instructions.
I promise that i will preserve the conditions.
Regards.

[therube]

As a start, backup ~/.config/FreeFileSync/ to something like, ~/tmp/FreeFileSync-thisconfigdoesnotwork/.

From there, can't hurt (I suppose) to post contents of that /FreeFileSync/ directory & the contents of the files therein.

[Zenju]

Okay, let's give it a try. Here are the updated instructions for Linux on how to create a crash dump file: https://freefilesync.org/faq.php#crash

And to make sure the crash dump matches the latest debugging symbols, here's the current Linux beta: https://www.mediafire.com/file/lprpiso1jt1sksw/FreeFileSync_13.1_beta_Linux.tar.gz

[Zenju]

From there, can't hurt (I suppose) to post contents of that /FreeFileSync/ directory & the contents of the files therein.

I also suspect that the crash might be reproducible with these specific config files.