[solved vdr-2.3.9] Uninitialised value was created by a heap allocation

valgrind --tool=memcheck --track-origins=yes ./vdr -Pfemon -P"satip  -d2 -s 192.168.178.129:554|DVBS2-4,DVBT2-2|minisatip" -P"vaapidevice  -d :0.0 -v va-api -a pulse -c softvol -w alsa-driver-broken -f "
==8422== Memcheck, a memory error detector
==8422== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==8422== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
==8422== Command: ./vdr -Pfemon -Psatip\ \ -d2\ -s\ 192.168.178.129:554|DVBS2-4,DVBT2-2|minisatip -Pvaapidevice\ \ -d\ :0.0\ -v\ va-api\ -a\ pulse\ -c\ softvol\ -w\ alsa-driver-broken\ -f\ 
==8422== 
==8422== Conditional jump or move depends on uninitialised value(s)
==8422==    at 0x1F822C: cDisplayChannel::ProcessKey(eKeys) (menu.c:4714)
==8422==    by 0x1F8BB7: cDisplayChannel::cDisplayChannel(eKeys) (menu.c:4654)
==8422==    by 0x19F05C: main (vdr.c:1466)
==8422==  Uninitialised value was created by a heap allocation
==8422==    at 0x4C3017F: operator new(unsigned long) (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==8422==    by 0x19F045: main (vdr.c:1466)
==8422==