pewu78

Thank you. Reproduced, attached log: [pihole-FTL.log](https://github.com/pi-hole/FTL/files/8357191/pihole-FTL.log)

Uploaded: https://tricorder.pi-hole.net/AO5euttP/ Below lines here: > [2022-04-03 04:26:19.952 12591M] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > [2022-04-03 04:26:19.952 12591M] ----------------------------> FTL crashed! [2022-04-03 04:26:19.952 12591M] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > [2022-04-03 04:26:19.952 12591M] Please report a bug at...

Yes, it still crashes with latest version. Output from the debugger: `Thread 1 "pihole-FTL" received signal SIGHUP, Hangup. Thread 1 "pihole-FTL" received signal SIGSEGV, Segmentation fault. __GI___libc_free (mem=0x2e) at malloc.c:3093...

I precisely followed instructions from the page you provided - attached gdb to the process and immediately resumed its execution by running continue long before it crashed. I didn't continue'd...

I ran the pihole -g with attached debugger and this time it didn't continue so I've managed to obtain backtrace. Here it is: ``` Thread 1 "pihole-FTL" received signal SIGHUP,...

Debug log: [https://tricorder.pi-hole.net/bX7irhHS/](url)

1. It didn't crash when sending HUP to pihole-FTL now. Last time it crashed only at the end of pihole -g command process (ran manually) and during weekly update, which...

Again it din't crash on scheduled update Gratity task. Still using fix/dhcp_netid_free branch.

Running fine so far, again passed todays update. Not too much logging either - about 6 entries of dhcp_netid_free() and 8 dhcp_netid_create() during this operation, none outside of it.

Today and last Sunday wasn't so good, pihole-FTL process was gone while _pihole status_ showed: ``` [✓] FTL is listening on port [✓] UDP (IPv4) [✓] TCP (IPv4) [✓] UDP...