FTL crashing everytime DB is written

FTL is crashing everytime data is saved to the FTL database.
My DBINTERVAL was set to 30... now set to 5 to test.
I tried to reboot my RPI.
I also tried to delete FTL DB file.

I'm using raspiBackup to do my daily backup on an external USB key.
this crash started happening right after the backup. It worked fine all day before this backup.
to make sure the FTL DB is consistent, I stop the FTL service before the backup.

FTL is not crashing when MAXDBDAYS is set to 0

here the FTL log for one of the crash:

[2020-03-31 06:10:00.311 736] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2020-03-31 06:10:00.311 736] ----------------------------> FTL crashed! <----------------------------
[2020-03-31 06:10:00.311 736] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2020-03-31 06:10:00.311 736] Please report a bug at Issues · pi-hole/FTL · GitHub
[2020-03-31 06:10:00.311 736] and include in your report already the following details:
[2020-03-31 06:10:00.311 736] FTL has been running for 462 seconds
[2020-03-31 06:10:00.311 736] FTL branch: release/v5.0
[2020-03-31 06:10:00.311 736] FTL version: vDev-b6364d0
[2020-03-31 06:10:00.311 736] FTL commit: b6364d0
[2020-03-31 06:10:00.311 736] FTL date: 2020-03-29 23:23:02 +0200
[2020-03-31 06:10:00.311 736] FTL user: started as pihole, ended as pihole
[2020-03-31 06:10:00.312 736] Compiled for armhf (compiled on CI) using arm-linux-gnueabihf-gcc (Debian 6.3.0-18) 6.3.0 20170516
[2020-03-31 06:10:00.312 736] Received signal: Segmentation fault
[2020-03-31 06:10:00.312 736] at address: 0x1
[2020-03-31 06:10:00.312 736] with code: SEGV_MAPERR (Address not mapped to object)
[2020-03-31 06:10:00.312 736] Backtrace:
[2020-03-31 06:10:00.312 736] B[0000]: 0x463618, /usr/bin/pihole-FTL(+0x23618) [0x463618]
[2020-03-31 06:10:00.312 736] B[0001]: 0xb6dae130, /lib/arm-linux-gnueabihf/libc.so.6(__default_rt_sa_restorer+0) [0xb6dae130]
[2020-03-31 06:10:00.313 736] B[0002]: 0x45bc1c, /usr/bin/pihole-FTL(parse_neighbor_cache+0x343) [0x45bc1c]
[2020-03-31 06:10:00.313 736] B[0003]: 0x45e5e8, /usr/bin/pihole-FTL(DB_thread+0xc7) [0x45e5e8]
[2020-03-31 06:10:00.313 736] ------ Listing content of directory /dev/shm ------
[2020-03-31 06:10:00.313 736] File Mode User:Group Filesize Filename
[2020-03-31 06:10:00.313 736] rwxrwxrwx root:root 260 .
[2020-03-31 06:10:00.313 736] rwxr-xr-x root:root 4K ..
[2020-03-31 06:10:00.313 736] rw------- pihole:pihole 4K FTL-per-client-regex
[2020-03-31 06:10:00.314 736] rw------- pihole:pihole 4K FTL-dns-cache
[2020-03-31 06:10:00.314 736] rw------- pihole:pihole 29K FTL-overTime
[2020-03-31 06:10:00.314 736] rw------- pihole:pihole 229K FTL-queries
[2020-03-31 06:10:00.314 736] rw------- pihole:pihole 20K FTL-upstreams
[2020-03-31 06:10:00.315 736] rw------- pihole:pihole 20K FTL-clients
[2020-03-31 06:10:00.315 736] rw------- pihole:pihole 66K FTL-domains
[2020-03-31 06:10:00.315 736] rw------- pihole:pihole 8K FTL-strings
[2020-03-31 06:10:00.316 736] rw------- pihole:pihole 12 FTL-settings
[2020-03-31 06:10:00.316 736] rw------- pihole:pihole 124 FTL-counters
[2020-03-31 06:10:00.316 736] rw------- pihole:pihole 28 FTL-lock
[2020-03-31 06:10:00.316 736] ---------------------------------------------------
[2020-03-31 06:10:00.316 736] Thank you for helping us to improve our FTL engine!
[2020-03-31 06:10:00.316 736] FTL terminated!

debug token https://tricorder.pi-hole.net/rk8w1qzdwn

adding some info about my system :
uname -a
Linux raspberrypi 4.19.97-v7l+ #1294 SMP Thu Jan 30 13:21:14 GMT 2020 armv7l GNU/Linux

pihole -v
Pi-hole version is v4.3.5-459-g0fad979 (Latest: v4.4)
AdminLTE version is v4.3.2-439-g6fdeee5 (Latest: v4.3.3)
FTL version is vDev-b6364d0 (Latest: v4.3.1)

/proc/cpuinfo
Hardware : BCM2835
Revision : c03111
Model : Raspberry Pi 4 Model B Rev 1.1

3 posts were merged into an existing topic: FTL crash after update v4.3.1