Hang when clicking OK in Preferences when home dir is on ext4 mount w/ sync flag

[cjritola]

XUbuntu 22.04
cqrlog 2.5.2 (PPA)
mariadb3 1:10.6.12-0ubuntu0.22
mariadb-client-10.6 [same]
mariadb-server-10.6 [same]
Intel NUC i3.

After OK is clicked, all console output (debug=5) is stopped, even hamlib poll output. OK button is frozen in pressed state.

gdb backtrace is not very helpful:

(gdb) bt 10
#0  0x000000000041f697 in  ()
#1  0x00000000044ecff0 in  ()
#2  0x00007fffffffb770 in  ()
#3  0x00007fffffffb4e0 in  ()
#4  0x000000000042030b in  ()
#5  0x00000000015d7f18 in  ()
#6  0x000000000062a87a in  ()
#7  0x00007fffffffb410 in  ()
#8  0x000000000048fc25 in  ()
#9  0x0000000000000000 in  ()

Seems to have started happening after upgrading to Ubuntu 22.04. Been running like this for a while. Still sort-of works.
Created a new log named 'test' on the opening menu, less lag with opening/closing sub-windows, but Preferences still hangs with OK. ~/.config/cqrlog/2cqrlog.cfg appears to be getting written over and over again in a loop.
Also hangs (or at least takes more than a few minutes) when clicking Close in QSO list. Again, button stuck in pressed state.
CPU usage is about 3% when hanging.
Closing application takes minutes. I only have a few hundred contacts logged. When using the empty 'test' log, the wait is about 7s. 'test' log backup is disabled in the 'test' log.
Tried "repair log database" feature in opening menu, no improvement.
Tried mv ~/.config/cqrlog ~/.config/cqrlog.old. It then thinks it's the first time running but no improvement.

xfce frequently states the application is unresponsive and offers to terminate it.

Also a long wait when closing windows in general, even Cancel in Preferences.

UPDATE:
Changing the fstab entry for the drive containing my home directory (it is then symlinked to /home/...) from sync to async fixed the hang issue in cqrlog. I do not yet see any change in performance of any other software so these hangs are still interesting in the context of cqrlog.

To the best of my knowledge at this time, to reproduce this issue is to use a home directory from an ext4 mount with the 'sync' flag.

Glad to have found the workaround. Works nicely now.