openskyd-dump1090 randolm stopps by NULL pointer

Hi,

On my Raspberry-pi zero based ADS-B receiver openskyd-dump1090 randomly stops working in a few hour or even more than a week after it starts.
If I go for a "systemctl restart opensky-feeder" then it restart and works fine until next occurrence of NULL pointer de-reference error. In this times I found similar logs in the system journal.

Aug 04 10:42:53 flighttracker kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000044
Aug 04 10:42:53 flighttracker kernel: pgd = 07d1528b
Aug 04 10:42:53 flighttracker kernel: [00000044] *pgd=17da1831, *pte=00000000, *ppte=00000000
Aug 04 10:42:53 flighttracker kernel: Internal error: Oops: 17 [#1] ARM
Aug 04 10:42:53 flighttracker kernel: Modules linked in: cmac bnep hci_uart btbcm serdev bluetooth ecdh_generic brcmfmac brcmutil sha256_generic cfg80211 snd_bcm2835(C) raspberrypi_hwmon snd_pcm hwmon rfk
Aug 04 10:42:53 flighttracker kernel: CPU: 0 PID: 505 Comm: openskyd-dump10 Tainted: G C 4.19.57+ #1244
Aug 04 10:42:53 flighttracker kernel: Hardware name: BCM2835
Aug 04 10:42:53 flighttracker kernel: PC is at perf_trace_hrtimer_init+0x28/0xd8
Aug 04 10:42:53 flighttracker kernel: LR is at vector_swi+0x3c/0x54
Aug 04 10:42:53 flighttracker kernel: pc : [<c0074d70>] lr : [<c00090fc>] psr: 60000093
Aug 04 10:42:53 flighttracker kernel: sp : d903df58 ip : d903dfb0 fp : d903dfac
Aug 04 10:42:53 flighttracker kernel: r10: c00090fc r9 : b4da4bf8 r8 : 60000010
Aug 04 10:42:53 flighttracker kernel: r7 : 00000107 r6 : b4da5470 r5 : c09e3028 r4 : 00000000
Aug 04 10:42:53 flighttracker kernel: r3 : 42196bf7 r2 : 42196bf7 r1 : b4da4bf8 r0 : bf76da77
Aug 04 10:42:53 flighttracker kernel: Flags: nZCv IRQs off FIQs on Mode SVC_32 ISA ARM Segment user
Aug 04 10:42:53 flighttracker kernel: Control: 00c5387d Table: 1a7fc008 DAC: 00000055
Aug 04 10:42:53 flighttracker kernel: Process openskyd-dump10 (pid: 505, stack limit = 0x5f1e5387)
Aug 04 10:42:53 flighttracker kernel: Stack: (0xd903df58 to 0xd903e000)
Aug 04 10:42:53 flighttracker kernel: df40: c0009d50 00c5387d
Aug 04 10:42:53 flighttracker kernel: df60: 00c5387d bf76da77 d903df94 008f162c 0002b8c8 00004000 00000121 bf76da77
Aug 04 10:42:53 flighttracker kernel: df80: d903dfa4 00000000 b4da4bf8 b4da5470 00000107 60000010 b6e88f88 00c5387d
Aug 04 10:42:53 flighttracker kernel: dfa0: 00000000 d903dfb0 c00090fc c0074d54 00000000 b4da4bf8 42196bf7 42196bf7
Aug 04 10:42:53 flighttracker kernel: dfc0: 00000000 b4da4bf8 b4da5470 00000107 bec0dc0a 00000001 00001000 b4da4fac
Aug 04 10:42:53 flighttracker kernel: dfe0: b6ee816c b4da4be8 00013830 b6e88f88 60000010 00000000 00000000 00000000
Aug 04 10:42:53 flighttracker kernel: [<c0074d70>] (perf_trace_hrtimer_init) from [<c00090fc>] (vector_swi+0x3c/0x54)
Aug 04 10:42:53 flighttracker kernel: Exception stack(0xd903dfb0 to 0xd903dff8)
Aug 04 10:42:53 flighttracker kernel: dfa0: 00000000 b4da4bf8 42196bf7 42196bf7
Aug 04 10:42:53 flighttracker kernel: dfc0: 00000000 b4da4bf8 b4da5470 00000107 bec0dc0a 00000001 00001000 b4da4fac
Aug 04 10:42:53 flighttracker kernel: dfe0: b6ee816c b4da4be8 00013830 b6e88f88 60000010 00000000
Aug 04 10:42:53 flighttracker kernel: Code: e1a09001 e5950000 e1a0a00e e50b0030 (e5941044)
Aug 04 10:42:53 flighttracker kernel: ---[ end trace 6c9d69cfdbfe665b ]---

My setup is based on an up-to-date Debian 9.9 version.
Opensky Feeder is installed from opensky-network.org/files/firmware/opens...der_latest_armhf.deb, and it is the latest and greatest: Version: 2.1.7-1

Does anybody have an idea how can it be fixed?
Or is there a monitoring what can restart the application in that casE?

Regards,
Botika